Triple
T17111827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latn |
E415243
|
entity |
| Predicate | isUsedOnAllContinents |
P11850
|
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: [Latn, isUsedOnAllContinents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedOnAllContinents Context triple: [Latn, isUsedOnAllContinents, true]
-
A.
usedInAllRegionsOf
Indicates that something is utilized or applied in every region within a specified scope or system.
-
B.
usedWorldwide
chosen
Indicates that something is utilized or applied across many countries or regions around the world.
-
C.
playedOnEveryFIFAContinent
Indicates that the subject has played (e.g., participated in matches) on at least one country within each of the official FIFA-recognized continental confederations.
-
D.
usedByCountriesWith
Indicates that something (such as an item, system, or practice) is utilized or employed by one or more specified countries in common.
-
E.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2bab0881908339ec7fb3ebe7e9 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.