Triple
T6489211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perth, Scotland |
E147991
|
entity |
| Predicate | regainedCityStatus |
P60434
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Perth, Scotland, regainedCityStatus, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regainedCityStatus Context triple: [Perth, Scotland, regainedCityStatus, 2012]
-
A.
cityStatusGrantedInMemoryOf
Indicates that city status was conferred on a place specifically to honor or commemorate a particular person, event, or entity.
-
B.
cityStatusGrantedIn
chosen
Indicates the event or point in time at which an entity was officially granted city status in a particular place or jurisdiction.
-
C.
cityStatusGrantedBy
Indicates that one entity (such as a person, authority, or institution) formally granted or conferred city status upon another entity (typically a settlement or locality).
-
D.
grantedCityStatusFor
Indicates that an authority has officially conferred city status upon an entity for a specified reason or basis.
-
E.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a97fff88190b6f993c14df62649 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.