Triple
T33217393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zirakzigil |
E850322
|
entity |
| Predicate | chronologicallyNotableEvent |
P194620
|
FINISHED |
| Object | Gandalf and Balrog battle in T.A. 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: Gandalf and Balrog battle in T.A. 3019 | Statement: [Zirakzigil, chronologicallyNotableEvent, Gandalf and Balrog battle in T.A. 3019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyNotableEvent Context triple: [Zirakzigil, chronologicallyNotableEvent, Gandalf and Balrog battle in T.A. 3019]
-
A.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
-
C.
notableInternationalEvents
Indicates that the subject is associated with significant events that have international relevance or impact.
-
D.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
E.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: May 1, 2026, 1:30 a.m.