Triple
T29661259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chern |
E750410
|
entity |
| Predicate | locatedInCountrySubdivisionCapitalRegion |
P167092
|
FINISHED |
| Object | Tula Oblast |
—
|
NE NERFINISHED |
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: Tula Oblast | Statement: [Chern, locatedInCountrySubdivisionCapitalRegion, Tula Oblast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountrySubdivisionCapitalRegion Context triple: [Chern, locatedInCountrySubdivisionCapitalRegion, Tula Oblast]
-
A.
capitalLocatedInRegion
chosen
Indicates that a capital city is geographically situated within a specific region.
-
B.
locatedInCountryCapitalOfProvince
Indicates that an entity is located in the country that contains the capital city of a specified province.
-
C.
capitalLocationRegion
Indicates that a location serves as the capital city or administrative center of a specified region.
-
D.
capitalOfSubdivision
Indicates that a place serves as the administrative capital of a specified subnational division (such as a state, province, or region).
-
E.
administrativeCenterInRegion
Indicates that one entity serves as the main administrative center (seat of government or administration) within a specified region.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: April 28, 2026, 6:58 p.m.