Triple
T32060761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Canadian |
E818739
|
entity |
| Predicate | presentInCity |
P12399
|
FINISHED |
| Object | Toronto |
—
|
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: Toronto | Statement: [Asian Canadian, presentInCity, Toronto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentInCity Context triple: [Asian Canadian, presentInCity, Toronto]
-
A.
isInCity
chosen
Indicates that one entity is located within the geographical boundaries of a specified city.
-
B.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
C.
usedInCity
Indicates that something is utilized, applied, or operates within the context or boundaries of a particular city.
-
D.
practicedInCity
Indicates that an activity, profession, or practice is carried out or has been performed within a particular city.
-
E.
endsInCity
Indicates that an entity (such as a route, trip, or movement) terminates or concludes within a specified city.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:21 a.m.