Triple
T1273622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natal |
E15763
|
entity |
| Predicate | provinceExistedFrom |
P28267
|
FINISHED |
| Object | 1910 |
—
|
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: 1910 | Statement: [Natal, provinceExistedFrom, 1910]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceExistedFrom Context triple: [Natal, provinceExistedFrom, 1910]
-
A.
previousProvince
Indicates that one province was the immediately preceding administrative region of another in a temporal or historical sequence.
-
B.
formerProvince
Indicates that an entity was previously a province of another entity but no longer holds that administrative status.
-
C.
hasPostalAbbreviationProvince
Indicates that a province is associated with a specific standardized postal abbreviation used in mailing addresses.
-
D.
province
Indicates that one entity is an administrative subdivision or region (a province) governed by or belonging to another, typically larger, political or territorial entity.
-
E.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
- F. None of above. chosen
Provenance (4 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c31400c08190a07ccb736df3bf54 |
completed | March 1, 2026, 10:52 p.m. |
Created at: March 1, 2026, 7:50 p.m.