Triple
T19345780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EcoWorld Ballymore |
E483872
|
entity |
| Predicate | developsPropertyType |
P135506
|
FINISHED |
| Object | apartment buildings |
—
|
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: apartment buildings | Statement: [EcoWorld Ballymore, developsPropertyType, apartment buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsPropertyType Context triple: [EcoWorld Ballymore, developsPropertyType, apartment buildings]
-
A.
developsStandardType
Indicates that an entity creates or establishes a particular type of standard.
-
B.
propertyTypeSpecialization
Indicates that one property type is a more specific or specialized version of another, more general property type.
-
C.
propertyType_rid
Indicates that an entity is associated with a specific property type identified by a unique resource identifier (RID).
-
D.
propertyType_rtx
Indicates that one entity has a specific type or category of property in relation to another entity.
-
E.
propertyTypeMix
Indicates that an entity involves or consists of a combination of different types of properties rather than a single uniform property type.
- F. None of above. chosen
Provenance (4 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185a56b4819089336564959b84df |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:34 p.m.