Triple
T10925002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TS |
E258041
|
entity |
| Predicate | stateCapitalRTOCodeExample |
P96679
|
FINISHED |
| Object | TS 09 (Hyderabad) |
—
|
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: TS 09 (Hyderabad) | Statement: [TS, stateCapitalRTOCodeExample, TS 09 (Hyderabad)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalRTOCodeExample Context triple: [TS, stateCapitalRTOCodeExample, TS 09 (Hyderabad)]
-
A.
stateCapitalRegion
Indicates that a region serves as the capital area or administrative seat for a particular state.
-
B.
stateCapitalForRegionLocatedAt
Indicates that a city serves as the capital of a particular region and is geographically located at that region.
-
C.
stateCapitalFunction
Indicates that one location serves as the official capital city and primary seat of government for a given state.
-
D.
stateCapitalStatus
Indicates that an entity serves as the official capital city of a specified state or state-level administrative region.
-
E.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7708f7ab48190b60a4bb8fdb17c8e |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:22 p.m.