Triple
T35319217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DHA Khayaban-e-Shahbaz |
E1019989
|
entity |
| Predicate | typicalPropertyUse |
P200030
|
FINISHED |
| Object | single-family houses |
—
|
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: single-family houses | Statement: [DHA Khayaban-e-Shahbaz, typicalPropertyUse, single-family houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPropertyUse Context triple: [DHA Khayaban-e-Shahbaz, typicalPropertyUse, single-family houses]
-
A.
typicalProperty
Indicates that a certain property is characteristically or commonly associated with an entity, reflecting what is typical for that entity.
-
B.
typicalSectorUse
Indicates the type of sector in which something is most commonly or characteristically used.
-
C.
hasTypicalBuildingUse
chosen
Indicates that something is generally or normally used for a particular type of building function or purpose.
-
D.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
E.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.