Triple
T2917778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frecce Tricolori |
E78647
|
entity |
| Predicate | numberOfAircraftInDisplay |
P5710
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Frecce Tricolori, numberOfAircraftInDisplay, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAircraftInDisplay Context triple: [Frecce Tricolori, numberOfAircraftInDisplay, 10]
-
A.
hasAircraftOnDisplay
Indicates that an entity exhibits or presents an aircraft as part of a display or collection.
-
B.
numberOfPlanes
chosen
Indicates the quantity of planes associated with or involved in a given entity or situation.
-
C.
aircraftCapacity
Indicates the maximum number of passengers or amount of load that an aircraft is designed or allowed to carry.
-
D.
planeNumber
Indicates that an entity is associated with a specific airplane identification number (such as a tail number or flight number).
-
E.
aircraftTypesCarried
Indicates that one entity (typically a vessel, facility, or platform) carries or is capable of carrying specific types of aircraft as part of its operations or configuration.
- 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.