Triple
T33152035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finwë |
E848462
|
entity |
| Predicate | ledEvent |
P176140
|
FINISHED |
| Object | Great Journey of the Elves |
—
|
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: Great Journey of the Elves | Statement: [Finwë, ledEvent, Great Journey of the Elves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledEvent Context triple: [Finwë, ledEvent, Great Journey of the Elves]
-
A.
enabledEvent
Indicates that one entity has activated or allowed a particular event to occur or be triggered.
-
B.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
-
C.
relayEvent
Indicates that one entity forwards, transmits, or passes along an event or message from a source to another recipient or system.
-
D.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69f3495a458c8190a1d34b237ba0be3f |
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. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:28 a.m.