Triple
T32695450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YTS |
E835993
|
entity |
| Predicate | locatedInOrServes |
—
|
GENERATED |
| Object | Timmins |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 1, 2026, 1:10 a.m.