Triple
T5637460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mighty Canadian Minebuster |
E124180
|
entity |
| Predicate | hasAirtime |
P64738
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mighty Canadian Minebuster, hasAirtime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirtime Context triple: [Mighty Canadian Minebuster, hasAirtime, true]
-
A.
airTime
Indicates the duration or scheduling time during which something, typically a broadcast or performance, is transmitted or presented.
-
B.
associatedFlagCarrier
Indicates that one entity serves as the designated national or primary flag carrier airline associated with another entity (such as a country, region, or organization).
-
C.
topUpMethod
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
D.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
E.
hasCellService
Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022820b7c81908f79c0a124d6b940 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:41 p.m.