Triple
T35059635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frecce Tricolori aircraft |
E1011558
|
entity |
| Predicate | primaryCurrentType |
P28113
|
FINISHED |
| Object | Aermacchi MB-339-A/PAN |
E309864
|
NE 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: Aermacchi MB-339-A/PAN | Statement: [Frecce Tricolori aircraft, primaryCurrentType, Aermacchi MB-339-A/PAN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCurrentType Context triple: [Frecce Tricolori aircraft, primaryCurrentType, Aermacchi MB-339-A/PAN]
-
A.
primaryCurrentUse
Indicates the main way something is currently being used or its principal present function.
-
B.
primaryType
chosen
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
C.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
primaryUserType
Indicates the main or dominant category of user associated with an entity or interaction.
-
E.
primaryConduitType
Indicates the main type or category of conduit used as the primary pathway for a connection or flow between entities.
- F. None of above.
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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37c63bbaac8190809699e4e52a206d |
completed | June 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.