Triple
T32695450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YTS |
E835993
|
entity |
| Predicate | locatedInOrServes |
P40
|
FINISHED |
| Object | Timmins |
E38453
|
NE 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: Timmins | Statement: [YTS, locatedInOrServes, Timmins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInOrServes Context triple: [YTS, locatedInOrServes, Timmins]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
servesAtLocation
Indicates that an entity provides its services or functions at a specified location.
-
C.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
D.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- F. None of above.
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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a030c7d03308190a102689db1e8b657 |
completed | May 12, 2026, 11:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34bce02b708190b7f6642b5a954792 |
completed | June 19, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_6a030a57b16c81909191270f64a77fcf |
completed | May 12, 2026, 11:09 a.m. |
Created at: May 1, 2026, 1:10 a.m.