Triple
T33111707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Kingship of the Dúnedain |
E847347
|
entity |
| Predicate | seatAfterRestoration |
P175585
|
FINISHED |
| Object | Minas Tirith |
—
|
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: Minas Tirith | Statement: [High Kingship of the Dúnedain, seatAfterRestoration, Minas Tirith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatAfterRestoration Context triple: [High Kingship of the Dúnedain, seatAfterRestoration, Minas Tirith]
-
A.
originalSeat
Indicates the seat that was initially assigned or occupied before any changes, moves, or reassignments occurred.
-
B.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in time.
-
C.
laterSeat
Indicates that one entity is seated in a position that comes after another entity in a specified ordering or sequence of seats.
-
D.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
-
E.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6eb33648190b26122f53c88d8eb |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d30b9e048190b0982e30b7fdfa3c |
completed | May 3, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:27 a.m.