Triple
T30633263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnor |
E779765
|
entity |
| Predicate | dividedUnderKing |
P170259
|
FINISHED |
| Object | Eärendur |
—
|
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: Eärendur | Statement: [Arnor, dividedUnderKing, Eärendur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dividedUnderKing Context triple: [Arnor, dividedUnderKing, Eärendur]
-
A.
kingdomDividedBy
Indicates that a kingdom is separated into distinct parts or regions by a specified boundary, event, or factor.
-
B.
dividedIn
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
-
C.
wasDividedBetween
Indicates that something was partitioned into portions that were allocated to two or more distinct recipients or groups.
-
D.
capitalDivision
Indicates that one administrative division serves as the capital of another administrative division or political entity.
-
E.
hadInternalDivision
Indicates that an entity experienced a split or conflict within its own members, factions, or components.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 29, 2026, 8:28 p.m.