Triple
T2917797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frecce Tricolori |
E78647
|
entity |
| Predicate | hasManeuver |
P22224
|
FINISHED |
| Object | bomb burst |
—
|
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: bomb burst | Statement: [Frecce Tricolori, hasManeuver, bomb burst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManeuver Context triple: [Frecce Tricolori, hasManeuver, bomb burst]
-
A.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
B.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
C.
navigationCondition
Indicates the specific circumstances or requirements that must be satisfied for a navigation action or route to be valid or taken.
-
D.
notableManeuver
chosen
Indicates that an entity is recognized for performing a specific maneuver, action, or tactical move that is considered notable or significant.
-
E.
withinDrivingRoute
Indicates that one location can be reached from another via a practical or allowable driving route, typically within a reasonable distance or time.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:54 p.m.