Triple
T859680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirupati |
E18570
|
entity |
| Predicate | hasUrbanAgglomerationStatus |
P17246
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tirupati, hasUrbanAgglomerationStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanAgglomerationStatus Context triple: [Tirupati, hasUrbanAgglomerationStatus, yes]
-
A.
containsUrbanArea
Indicates that a geographic region fully or partially encompasses an urbanized area within its boundaries.
-
B.
belongsToIntercommunality
Indicates that an entity is a member of, or administratively attached to, a specific intercommunal structure or grouping.
-
C.
urbanAreaType
Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
-
D.
isUrbanized
chosen
Indicates that a place or area has been developed with dense human settlement, infrastructure, and built environment characteristic of a city or town.
-
E.
isSubProvincialCity
Indicates that a city holds a sub-provincial administrative status, ranking below a province but above ordinary prefecture-level cities in the governmental hierarchy.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac50e5ec81908ac0c4b7123b4ebb |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.