Triple
T37980228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Bout |
E947530
|
entity |
| Predicate | usedBusinessCover |
P65448
|
FINISHED |
| Object | cargo airline companies |
—
|
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: cargo airline companies | Statement: [Viktor Bout, usedBusinessCover, cargo airline companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBusinessCover Context triple: [Viktor Bout, usedBusinessCover, cargo airline companies]
-
A.
usedCover
chosen
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
B.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
C.
previouslyCovered
Indicates that the subject has already been addressed, discussed, or dealt with at an earlier time or in a prior context.
-
D.
ownershipCover
Indicates that one entity’s ownership or control extends over, protects, or encompasses another entity.
-
E.
mayCover
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:20 p.m.