Triple
T27769863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adiala Road area |
E701713
|
entity |
| Predicate | commonPropertyType |
P151371
|
FINISHED |
| Object | small housing plots |
—
|
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: small housing plots | Statement: [Adiala Road area, commonPropertyType, small housing plots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPropertyType Context triple: [Adiala Road area, commonPropertyType, small housing plots]
-
A.
propertiesType
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
-
B.
typicalProperty
chosen
Indicates that a certain property is characteristically or commonly associated with an entity, reflecting what is typical for that entity.
-
C.
propertyTypeOf
Indicates that one entity is the type or category of property to which another entity belongs.
-
D.
commonField
Indicates that two or more entities share at least one field, attribute, or data element in common.
-
E.
commonAttribute
Indicates that two or more entities share the same specified attribute or property.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 4:34 p.m.