Triple
T9825415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard Payne |
E238641
|
entity |
| Predicate | conditionForBomb |
P88555
|
FINISHED |
| Object | bus speed must stay above 50 miles per hour |
—
|
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: bus speed must stay above 50 miles per hour | Statement: [Howard Payne, conditionForBomb, bus speed must stay above 50 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionForBomb Context triple: [Howard Payne, conditionForBomb, bus speed must stay above 50 miles per hour]
-
A.
detonationCondition
chosen
Indicates the specific circumstances or triggers under which a detonation occurs or is initiated.
-
B.
numberOfFailedBombs
Indicates the count of bombs associated with an entity that did not successfully detonate or function as intended.
-
C.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
D.
numberOfBombs
Indicates the quantity of bombs associated with a given entity or situation.
-
E.
conditionForBattle
Indicates that one situation, state, or requirement must be satisfied in order for a battle or combat event to occur.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3181c688190afea3b27ee392a30 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.