Triple
T7872867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyderabad-Karnataka |
E182779
|
entity |
| Predicate | developmentFocusArea |
P73050
|
FINISHED |
| Object | education |
—
|
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: education | Statement: [Hyderabad-Karnataka, developmentFocusArea, education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentFocusArea Context triple: [Hyderabad-Karnataka, developmentFocusArea, education]
-
A.
developmentArea
Indicates the geographic or conceptual region within which development, construction, or growth activities are planned, permitted, or occurring.
-
B.
developmentPillar
Indicates that one entity serves as a fundamental pillar or core focus area supporting the development or growth of another entity.
-
C.
developmentLinkedTo
Indicates that the development or progression of one entity is causally or contextually connected to the development or progression of another entity.
-
D.
development
Indicates a process or relationship in which something grows, advances, or becomes more complex or mature over time.
-
E.
developmentCategory
chosen
Indicates the classification of an entity according to a particular stage, type, or area of development.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a6d93881908d68386e49bea1e3 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:56 p.m.