Triple
T2422530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAP Air Portugal |
E53449
|
entity |
| Predicate | primaryHubFunction |
P38473
|
FINISHED |
| Object | connecting Europe with South America |
—
|
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: connecting Europe with South America | Statement: [TAP Air Portugal, primaryHubFunction, connecting Europe with South America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHubFunction Context triple: [TAP Air Portugal, primaryHubFunction, connecting Europe with South America]
-
A.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
B.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
C.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
D.
primaryFunctionContext
Indicates the main situational or operational context in which a function, role, or process is primarily intended to be used or performed.
-
E.
primaryBus
Indicates that one entity functions as the main or principal bus associated with another entity within a system or configuration.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc9f1ba608190b488874bed3533dd |
completed | March 7, 2026, 6:47 a.m. |
Created at: March 6, 2026, 9:42 p.m.