Triple
T30633282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnor |
E779765
|
entity |
| Predicate | notableHeir |
P4268
|
FINISHED |
| Object | Aragorn II Elessar |
E868881
|
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: Aragorn II Elessar | Statement: [Arnor, notableHeir, Aragorn II Elessar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHeir Context triple: [Arnor, notableHeir, Aragorn II Elessar]
-
A.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableDescent
chosen
Indicates a genealogical relationship where one entity is a descendant of another in a way considered historically, culturally, or socially significant.
-
D.
sonNotableFor
Indicates that a son is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
notableCrownPrincess
Indicates that the person holds or held the title of crown princess and is distinguished or noteworthy in that role.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28c7b5b1ac8190a54a1396b2afe574 |
completed | June 10, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:28 p.m.