Triple
T32097331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gandalf at the Bridge of Khazad-dûm |
E819751
|
entity |
| Predicate | setInAge |
P98262
|
FINISHED |
| Object | Third Age |
—
|
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: Third Age | Statement: [Gandalf at the Bridge of Khazad-dûm, setInAge, Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInAge Context triple: [Gandalf at the Bridge of Khazad-dûm, setInAge, Third Age]
-
A.
setsMinimumAge
Indicates that an entity establishes the lowest permissible age required for participation, access, or eligibility in relation to another entity or activity.
-
B.
ageSetting
Indicates that one entity specifies, adjusts, or defines the age value or age-related parameter of another entity.
-
C.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
D.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
E.
existsInAge
chosen
Indicates that an entity is present, valid, or active during a specified age or time period.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:26 a.m.