Triple
T36557448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elves of Lindon |
E901733
|
entity |
| Predicate | ledByInWar |
P176415
|
FINISHED |
| Object | Gil-galad |
—
|
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: Gil-galad | Statement: [Elves of Lindon, ledByInWar, Gil-galad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledByInWar Context triple: [Elves of Lindon, ledByInWar, Gil-galad]
-
A.
battleLedTo
Indicates that one battle resulted in, caused, or directly brought about another event, state, or outcome.
-
B.
usedInWar
Indicates that something (such as a resource, technology, or strategy) was employed as part of military activities or conflict in a war.
-
C.
ledByDuringWarOfTheRing
chosen
Indicates that an individual or group served as the leader of another entity specifically during the period of the War of the Ring.
-
D.
almostLedToWarIn
Indicates that one entity’s actions or circumstances brought it very close to causing a war in a specified place or context, but the war ultimately did not occur.
-
E.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.