Triple
T7834465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun City |
E181655
|
entity |
| Predicate | describesUrbanFeatureOf |
P58917
|
FINISHED |
| Object | blue houses of Jodhpur |
—
|
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: blue houses of Jodhpur | Statement: [Sun City, describesUrbanFeatureOf, blue houses of Jodhpur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesUrbanFeatureOf Context triple: [Sun City, describesUrbanFeatureOf, blue houses of Jodhpur]
-
A.
hasUrbanFeature
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
-
B.
cityDescribedAs
chosen
Indicates that a city is characterized or portrayed using a particular description, label, or set of attributes.
-
C.
iconicFeature
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
-
D.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
E.
sceneFeature
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb064b872081908e269f4fe1b85436 |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:45 p.m.