Triple
T29050066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Charlotte City |
E735241
|
entity |
| Predicate | usedToBeOfficialNameUntil |
P62748
|
FINISHED |
| Object | 21 June 2022 |
—
|
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: 21 June 2022 | Statement: [Queen Charlotte City, usedToBeOfficialNameUntil, 21 June 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToBeOfficialNameUntil Context triple: [Queen Charlotte City, usedToBeOfficialNameUntil, 21 June 2022]
-
A.
formerOfficialNameOf
chosen
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
-
B.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
-
C.
officialNameSince
Indicates the date or point in time from which a particular official name has been in effect for an entity.
-
D.
laterOfficialName
Indicates that an entity was known by one name at an earlier time and was officially renamed to a different name at a later time.
-
E.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 10:07 a.m.