Triple
T9573188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa Holdings S.A. |
E230977
|
entity |
| Predicate | coreAssetType |
P15055
|
FINISHED |
| Object | airline equity interests |
—
|
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: airline equity interests | Statement: [Copa Holdings S.A., coreAssetType, airline equity interests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreAssetType Context triple: [Copa Holdings S.A., coreAssetType, airline equity interests]
-
A.
assetType
chosen
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
B.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
C.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
D.
mainAssetManaged
Indicates that one entity is responsible for managing another entity that serves as the primary or main asset.
-
E.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998d79cc8190b94e5953915a5fa4 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.