Triple
T15104549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asas de Portugal |
E360753
|
entity |
| Predicate | hasDisplayDiscipline |
P117338
|
FINISHED |
| Object | close formation flying |
—
|
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: close formation flying | Statement: [Asas de Portugal, hasDisplayDiscipline, close formation flying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplayDiscipline Context triple: [Asas de Portugal, hasDisplayDiscipline, close formation flying]
-
A.
hasDisciplineSystem
Indicates that an entity possesses or is governed by a particular system of rules, methods, or practices for maintaining discipline.
-
B.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
-
C.
hasAwardedDiscipline
Indicates that one entity has formally imposed or granted a disciplinary action or sanction upon another entity.
-
D.
featuredDiscipline
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
-
E.
hasPrimaryDisciplineStructure
Indicates that an entity is associated with its main or principal organizational or structural form of discipline.
- F. None of above. chosen
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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00551521c8190b48d1a074bb4bdfc |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:05 a.m.