Triple
T24842141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binter Cabo Verde |
E621643
|
entity |
| Predicate | hasSubsidiaryRelationWith |
P80692
|
FINISHED |
| Object | Binter Canarias |
—
|
NE NERFINISHED |
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: Binter Canarias | Statement: [Binter Cabo Verde, hasSubsidiaryRelationWith, Binter Canarias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiaryRelationWith Context triple: [Binter Cabo Verde, hasSubsidiaryRelationWith, Binter Canarias]
-
A.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
-
B.
usedBySubsidiaryOf
Indicates that something is used by an entity that is a subsidiary of another organization.
-
C.
hasAllianceThroughSubsidiary
Indicates that two entities are in an alliance indirectly, established or maintained through one or more subsidiary entities rather than directly between the primary entities.
-
D.
hasSubsidiaryTop
Indicates that one organization is the primary or top-level parent of another organization that operates as its subsidiary.
-
E.
hasSubsidiaryBusiness
chosen
Indicates that one business entity owns or controls another business entity as its subsidiary.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:19 a.m.