Triple
T37565769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwindor |
E933949
|
entity |
| Predicate | statusAfterAngband |
P88730
|
FINISHED |
| Object | Broken and aged |
—
|
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: Broken and aged | Statement: [Gwindor, statusAfterAngband, Broken and aged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterAngband Context triple: [Gwindor, statusAfterAngband, Broken and aged]
-
A.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
B.
statusAfterSmaug
chosen
Indicates the resulting status or condition of an entity after an event or interaction involving Smaug has occurred.
-
C.
statusAfterEvents
Indicates the resulting status or condition of an entity after one or more specified events have occurred.
-
D.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
E.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 3, 2026, 4:17 p.m.