Triple
T24581205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ball |
E608254
|
entity |
| Predicate | restartTypes |
P88022
|
FINISHED |
| Object | kick-off |
—
|
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: kick-off | Statement: [The Ball, restartTypes, kick-off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restartTypes Context triple: [The Ball, restartTypes, kick-off]
-
A.
startFinishType
Indicates the specific way in which an activity, event, or process begins and/or ends (e.g., its initiation and completion characteristics).
-
B.
restartPolicy
chosen
Indicates the rules governing if and how an action, process, or task should automatically restart after it stops or fails.
-
C.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
D.
resetType
Indicates the specific kind or method of reset applied to an entity, process, or system state.
-
E.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a982db00819081038adce05c0b52 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.