Triple
T37467436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuse |
E931065
|
entity |
| Predicate | revealEvent |
P37746
|
FINISHED |
| Object | E3 2011 |
—
|
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: E3 2011 | Statement: [Fuse, revealEvent, E3 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealEvent Context triple: [Fuse, revealEvent, E3 2011]
-
A.
peakEvent
Indicates the occurrence of a maximum or most intense point within a process, activity, or measurable phenomenon.
-
B.
discoveryEvent
chosen
Indicates an event in which something previously unknown or unrecognized is found, identified, or revealed.
-
C.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
-
D.
reportsEventsAt
Indicates that one entity provides information or reports about events occurring at a specific location or time.
-
E.
relayEvent
Indicates that one entity forwards, transmits, or passes along an event or message from a source to another recipient or system.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.