Triple
T28272589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiguan Mansions |
E712896
|
entity |
| Predicate | hasBuildingLayout |
P41702
|
FINISHED |
| Object | courtyard layout |
—
|
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: courtyard layout | Statement: [Xiguan Mansions, hasBuildingLayout, courtyard layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingLayout Context triple: [Xiguan Mansions, hasBuildingLayout, courtyard layout]
-
A.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
B.
hasBuildingLocation
Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
-
C.
hasFloorPlanShape
chosen
Indicates that an entity has a specific geometric or structural configuration defining the shape of its floor plan.
-
D.
hasUrbanLayoutType
Indicates that an entity possesses or is characterized by a specific type or pattern of urban spatial layout.
-
E.
hasBuildingForm
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 11:18 p.m.