Triple
T33152071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reunited Kingdom of Arnor and Gondor |
E848463
|
entity |
| Predicate | containsFormerEntity |
P201657
|
FINISHED |
| Object | Arnor |
—
|
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: Arnor | Statement: [Reunited Kingdom of Arnor and Gondor, containsFormerEntity, Arnor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFormerEntity Context triple: [Reunited Kingdom of Arnor and Gondor, containsFormerEntity, Arnor]
-
A.
hasFormerEntity
Indicates that one entity previously existed in a different form, role, or identity that is represented by another entity.
-
B.
isFormerEntity
Indicates that an entity previously held a particular status, role, or identity but no longer does so.
-
C.
appliesToFormerEntity
Indicates that the relationship or action is directed toward or relevant to an entity in its previous or former state, rather than its current one.
-
D.
hasFormerStructure
Indicates that an entity previously had a particular structural form or configuration that has since changed.
-
E.
containsFormerlyNamed
Indicates that one entity currently contains another entity that was previously known by a different name.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
| PDg | Predicate description generation | batch_6a0010e304a08190a4d0a4fa11a9a3b3 |
completed | May 10, 2026, 5 a.m. |
Created at: May 1, 2026, 1:28 a.m.