Triple
T14916621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria City |
E371398
|
entity |
| Predicate | usedAsOfficialDesignationUntil |
P12531
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Victoria City, usedAsOfficialDesignationUntil, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsOfficialDesignationUntil Context triple: [Victoria City, usedAsOfficialDesignationUntil, mid-20th century]
-
A.
formerDesignation
chosen
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
officiallyAdopted
Indicates that an entity has been formally accepted, approved, or enacted by an authorized body or process as the recognized standard or version.
-
C.
yearDesignated
Indicates the specific year in which something was formally designated, assigned, or given an official status.
-
D.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
E.
previousDesignationEstablished
Indicates that an earlier official designation or title for an entity was formally created or put into effect.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62038508190946499cd3552990e |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:31 a.m.