Triple
T36547525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Bëor |
E901174
|
entity |
| Predicate | survivorsLedBy |
P185839
|
FINISHED |
| Object | Emeldir the Manhearted |
—
|
NE NERFINISHED |
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: Emeldir the Manhearted | Statement: [House of Bëor, survivorsLedBy, Emeldir the Manhearted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorsLedBy Context triple: [House of Bëor, survivorsLedBy, Emeldir the Manhearted]
-
A.
isSurvivorOf
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
B.
survivorsJourney
Indicates the ongoing process or path a survivor takes as they cope with, adapt to, and move forward from a traumatic or life-threatening experience.
-
C.
survivorWith
Indicates a relationship where one entity survives an event or condition together with, or in the presence of, another entity.
-
D.
survivorsOnRaft
Indicates that certain individuals remain alive and present together on a specific raft after a hazardous or catastrophic event.
-
E.
survivorsLandingPlace
Indicates the location where survivors arrived or were brought after an incident or event.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.