Triple
T33111693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Kingship of the Dúnedain |
E847347
|
entity |
| Predicate | temporarilyDividedBetween |
P6497
|
FINISHED |
| Object | Kings of 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: Kings of Arnor | Statement: [High Kingship of the Dúnedain, temporarilyDividedBetween, Kings of Arnor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyDividedBetween Context triple: [High Kingship of the Dúnedain, temporarilyDividedBetween, Kings of Arnor]
-
A.
dividedBetween
chosen
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
B.
wasDividedBetween
Indicates that something was partitioned into portions that were allocated to two or more distinct recipients or groups.
-
C.
sometimesDividedInto
Indicates that an entity is on some occasions partitioned or separated into distinct parts, sections, or groups, but not always.
-
D.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
-
E.
dividedIn
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
- F. None of above.
Provenance (3 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:27 a.m.