Triple
T32498262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MD4 |
E830583
|
entity |
| Predicate | collisionFound |
P174897
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MD4, collisionFound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionFound Context triple: [MD4, collisionFound, true]
-
A.
collisionResult
Indicates the outcome or consequence that occurs when two or more entities collide.
-
B.
collision
Indicates that two or more entities come into contact with each other at the same place and time, typically involving an impact or crash.
-
C.
collisionType
Indicates the specific kind or category of collision that occurs between two or more entities.
-
D.
collisionAttackKnown
Indicates that a collision-based attack method or vulnerability is known or has been discovered.
-
E.
marksCollisionBetween
Indicates a recorded event or state where two or more entities have come into contact or collided with each other.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: May 1, 2026, 12:59 a.m.