Triple
T34326749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutland, England |
E880883
|
entity |
| Predicate | historicCountyStatusRestored |
P202156
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Rutland, England, historicCountyStatusRestored, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCountyStatusRestored Context triple: [Rutland, England, historicCountyStatusRestored, 1997]
-
A.
historicCountyStatusRetained
Indicates that an entity has maintained or preserved its official status as a historic county without interruption or loss.
-
B.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
C.
historicCountyPart
Indicates that one entity forms a constituent part or subdivision of a historic county.
-
D.
historicCountyAbolishedAsAdministrativeUnit
Indicates that a historic county ceased to function as an official administrative unit.
-
E.
historicParliamentaryCounty
Indicates that an entity is (or was) located within, or associated with, a historic parliamentary county as defined for electoral or administrative purposes.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
| PDg | Predicate description generation | batch_6a005b2cdbc881908b433623e3252df5 |
completed | May 10, 2026, 10:17 a.m. |
Created at: May 1, 2026, 1:58 a.m.