Triple
T28655539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Best Special Event |
E725319
|
entity |
| Predicate | eventTypeRecognized |
P167370
|
FINISHED |
| Object | one-off events |
—
|
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: one-off events | Statement: [Best Special Event, eventTypeRecognized, one-off events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypeRecognized Context triple: [Best Special Event, eventTypeRecognized, one-off events]
-
A.
eventTypeCaptured
Indicates that the specific type or category of an event has been successfully recorded or logged.
-
B.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
-
C.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
D.
componentEventType
Indicates the type or category of event associated with a specific component.
-
E.
discoveryEvent
Indicates an event in which something previously unknown or unrecognized is found, identified, or revealed.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 4:55 a.m.