Triple
T33111701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Kingship of the Dúnedain |
E847347
|
entity |
| Predicate | restoredInYearApprox |
P8589
|
FINISHED |
| Object | Third Age 3019 |
—
|
LITERAL 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: Third Age 3019 | Statement: [High Kingship of the Dúnedain, restoredInYearApprox, Third Age 3019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredInYearApprox Context triple: [High Kingship of the Dúnedain, restoredInYearApprox, Third Age 3019]
-
A.
reconstructionOrRestorationDate
chosen
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
B.
restoredInAge
Indicates that something was brought back to a previous or improved state during a specific age or time period.
-
C.
recoveredYear
Indicates the year in which something that was lost, damaged, or unwell was successfully restored, retrieved, or brought back to a desired state.
-
D.
restoredVersionReleaseYear
Indicates the year in which a restored version of an existing work was released.
-
E.
restorationPremieredAt
Indicates that a particular restoration of a work had its first public showing or debut at a specific event, venue, or location.
- 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_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:27 a.m.