Triple
T37350365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IOC |
E927303
|
entity |
| Predicate | hasMineAt |
P73907
|
FINISHED |
| Object | Labrador City, Newfoundland and Labrador, Canada |
—
|
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: Labrador City, Newfoundland and Labrador, Canada | Statement: [IOC, hasMineAt, Labrador City, Newfoundland and Labrador, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMineAt Context triple: [IOC, hasMineAt, Labrador City, Newfoundland and Labrador, Canada]
-
A.
hasNotableMine
Indicates that an entity possesses or is associated with a mine considered significant or noteworthy in some context.
-
B.
hasNearbyMine
Indicates that one entity is located close to or in the vicinity of a mine associated with another entity.
-
C.
hasMineType
Indicates that an entity is associated with or characterized by a specific type or category of mine.
-
D.
hasHistoricMine
Indicates that an entity possesses, contains, or is the site of a mine that is of historical significance.
-
E.
associatedMine
chosen
Indicates that one entity is linked or connected to a particular mine, typically as its source, location, or relevant mining site.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:16 p.m.