Triple
T36556139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dor-en-Ernil |
E901702
|
entity |
| Predicate | hasNotableLord |
P203783
|
FINISHED |
| Object | Imrahil, Prince of Dol Amroth |
E740402
|
NE 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: Imrahil, Prince of Dol Amroth | Statement: [Dor-en-Ernil, hasNotableLord, Imrahil, Prince of Dol Amroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLord Context triple: [Dor-en-Ernil, hasNotableLord, Imrahil, Prince of Dol Amroth]
-
A.
hasNotableBarony
Indicates that an entity possesses or is associated with a barony that is considered notable or significant in some context.
-
B.
notableLordship
chosen
Indicates that an entity holds or has held a particularly significant or distinguished lordship over another entity or domain.
-
C.
hasNotableDukedom
Indicates that an entity holds or is associated with a dukedom that is considered historically or culturally significant.
-
D.
hasNotableMarquessate
Indicates that an entity holds or is associated with a marquessate that is considered historically or socially notable.
-
E.
hasLordSpeaker
Indicates that one entity serves as the Lord Speaker (presiding officer) of another entity, typically a parliamentary or legislative body.
- F. None of above.
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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39e6f034fc8190af0ebae6ade6f48b |
completed | June 23, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.