Triple
T24067546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipal Borough of Edmonton |
E596131
|
entity |
| Predicate | gainedStatusIn |
P38040
|
FINISHED |
| Object | 1937 |
—
|
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: 1937 | Statement: [Municipal Borough of Edmonton, gainedStatusIn, 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedStatusIn Context triple: [Municipal Borough of Edmonton, gainedStatusIn, 1937]
-
A.
strengthenedStatusOf
Indicates that the status, condition, or standing of one entity has been made stronger or more robust in relation to another entity or context.
-
B.
statusGrantedOn
Indicates the date or time at which a particular status was officially conferred or became effective for an entity.
-
C.
obtainedStatus
chosen
Indicates that an entity has received or achieved a particular status or condition as a result of some process or event.
-
D.
gainedUniversityStatus
Indicates that an institution has officially achieved recognition or designation as a university.
-
E.
gained
Indicates that one entity has come to possess, acquire, or increase in something (such as an object, quality, or amount) relative to another point or state.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5c57e88190ba05cc41b8fd035a |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:40 p.m.