Triple
T32015237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohannon Development Company |
E817518
|
entity |
| Predicate | typeOfPropertyDeveloped |
P135506
|
FINISHED |
| Object | shopping centers |
—
|
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: shopping centers | Statement: [Bohannon Development Company, typeOfPropertyDeveloped, shopping centers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPropertyDeveloped Context triple: [Bohannon Development Company, typeOfPropertyDeveloped, shopping centers]
-
A.
developsPropertyType
chosen
Indicates that an entity is responsible for creating, constructing, or bringing into existence a specific type of property.
-
B.
propertyType_y
Indicates that one entity has a specific type or category of property in relation to another entity.
-
C.
propertyType_id
Indicates a relationship that specifies the type or category of a property associated with an entity.
-
D.
propertyTypeOf
Indicates that one entity is the type or category of property to which another entity belongs.
-
E.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: May 1, 2026, 12:16 a.m.