Triple
T27962107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Società per Azioni Esercizi Aeroportuali |
E704603
|
entity |
| Predicate | hasCoreAsset |
P7587
|
FINISHED |
| Object | Milan airport system |
—
|
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: Milan airport system | Statement: [Società per Azioni Esercizi Aeroportuali, hasCoreAsset, Milan airport system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreAsset Context triple: [Società per Azioni Esercizi Aeroportuali, hasCoreAsset, Milan airport system]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasAsset
chosen
Indicates that one entity possesses, owns, or controls another entity as an asset.
-
C.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
D.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
E.
hasCoreRequirement
Indicates that one entity is a mandatory prerequisite or essential condition that must be satisfied for another entity.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: April 27, 2026, 7:32 p.m.