Triple
T11047743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men (Middle-earth) |
E261174
|
entity |
| Predicate | calledSecondbornBy |
P97486
|
FINISHED |
| Object | Elves |
—
|
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: Elves | Statement: [Men (Middle-earth), calledSecondbornBy, Elves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calledSecondbornBy Context triple: [Men (Middle-earth), calledSecondbornBy, Elves]
-
A.
calledHimself
Indicates that a person referred to or identified himself using a particular name, title, or description.
-
B.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
-
C.
secondCreatedBy
Indicates that an entity was created by a second or subsequent creator, distinguishing this creator from the primary or original one.
-
D.
secondGenerationName
Indicates that the object is the name given to the second generation derived from the subject.
-
E.
willBeBornAs
Indicates that an entity is predicted or destined to come into existence in the future as a particular individual or form.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798315b988190bc565581b2664009 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.