Triple
T29784684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Greater Toronto Area |
E756227
|
entity |
| Predicate | notOfficialAdministrativeUnit |
P13450
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Eastern Greater Toronto Area, notOfficialAdministrativeUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notOfficialAdministrativeUnit Context triple: [Eastern Greater Toronto Area, notOfficialAdministrativeUnit, true]
-
A.
notOfficialNameOf
chosen
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
B.
notOfficialIn
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or jurisdiction.
-
C.
notOfficiallyProclaimedBy
Indicates that something has not been formally or legally announced, declared, or recognized by the specified authority or entity.
-
D.
hasNoOfficialName
Indicates that the entity does not have an officially recognized or formally assigned name.
-
E.
notIncorporatedAs
Indicates that an entity has not been legally formed, registered, or recognized as a corporation or similar incorporated organization.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674a9cc8481909068fcdcc8ed7dab |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:08 p.m.