Triple
T22623135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marg |
E558338
|
entity |
| Predicate | oftenGivenTo |
P148961
|
FINISHED |
| Object | girls |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: girls | Statement: [Marg, oftenGivenTo, girls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenGivenTo Context triple: [Marg, oftenGivenTo, girls]
-
A.
mayBeGivenTo
Indicates that something is permitted or eligible to be transferred, assigned, or provided from one entity to another.
-
B.
originallyGivenTo
Indicates that something was first transferred, assigned, or presented to a particular recipient before any later changes in ownership or status.
-
C.
givenFor
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
-
D.
treatsOf
Indicates that a work, statement, or discourse deals with, discusses, or is concerned with a particular subject or topic.
-
E.
historicallyGivenTo
Indicates that something was transferred or bestowed upon an entity at some point in the past, typically as recorded or recognized in historical accounts.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3b97f8819082ea2b23ff4b2173 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:01 p.m.