Triple
T29032003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Realm of Gondor |
E737751
|
entity |
| Predicate | notableLordship |
P203783
|
FINISHED |
| Object | Princedom of Dol Amroth |
E908147
|
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: Princedom of Dol Amroth | Statement: [Realm of Gondor, notableLordship, Princedom of Dol Amroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLordship Context triple: [Realm of Gondor, notableLordship, Princedom of Dol Amroth]
-
A.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
B.
lordshipType
Indicates the specific kind or category of lordship relationship that exists between one entity and another.
-
C.
hasNotableBarony
Indicates that an entity possesses or is associated with a barony that is considered notable or significant in some context.
-
D.
lordshipHeldIn
Indicates that an entity holds or exercises lordship, authority, or feudal control within a specified place or territorial jurisdiction.
-
E.
lordshipCreated
Indicates that a lordship was formally established or brought into existence.
- F. None of above. chosen
Provenance (5 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a020243e2b4819086dbfdcf4372405e |
completed | May 11, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a251f695ca481908026b9ea02c85ca7 |
completed | June 7, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_6a0200f585bc8190b774c54cec409b00 |
completed | May 11, 2026, 4:16 p.m. |
| PDg | Predicate description generation | batch_6a0202432fb08190abf6b83cd7da8deb |
completed | May 11, 2026, 4:22 p.m. |
Created at: April 28, 2026, 9:56 a.m.