Triple
T30834912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latapie House |
E785332
|
entity |
| Predicate | hasInteriorOrganization |
P117959
|
FINISHED |
| Object | open-plan living area |
—
|
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: open-plan living area | Statement: [Latapie House, hasInteriorOrganization, open-plan living area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorOrganization Context triple: [Latapie House, hasInteriorOrganization, open-plan living area]
-
A.
interiorOrganization
chosen
Indicates how the internal parts or elements of something are arranged, structured, or organized in relation to one another.
-
B.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
C.
hasInteriorBehavior
Indicates that an entity exhibits a particular behavior or set of behaviors within its internal or enclosed space.
-
D.
hasInteriorItem
Indicates that one entity contains another entity as an item located within its interior.
-
E.
hasOrganizationalStructure
Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: April 29, 2026, 8:45 p.m.