Triple
T30086084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCM Partnership |
E764603
|
entity |
| Predicate | locationOfClientBase |
P60205
|
FINISHED |
| Object | Vancouver |
—
|
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: Vancouver | Statement: [MCM Partnership, locationOfClientBase, Vancouver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfClientBase Context triple: [MCM Partnership, locationOfClientBase, Vancouver]
-
A.
baseLocation
chosen
Indicates the primary place where an entity is based, headquartered, or operates from as its main location.
-
B.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
-
C.
coreLocation
Indicates that one entity serves as the central or primary location associated with another entity.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00a15604fc8190b1c280794960f3a4 |
completed | May 10, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_6a00a0f7e77881909ac85755ab0e6329 |
completed | May 10, 2026, 3:15 p.m. |
Created at: April 29, 2026, 7:04 p.m.