Triple
T8991523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Najdi architecture |
E214799
|
entity |
| Predicate | typicalBuildingFunction |
P1844
|
FINISHED |
| Object | residential houses |
—
|
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: residential houses | Statement: [Najdi architecture, typicalBuildingFunction, residential houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBuildingFunction Context triple: [Najdi architecture, typicalBuildingFunction, residential houses]
-
A.
hasBuildingFunction
Indicates that a building is used for or serves a particular function or purpose.
-
B.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
seatBuildingFunction
Indicates that a building or structure serves a seating-related function, such as providing places for people to sit or be accommodated.
-
D.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
E.
featuresBuilding
Indicates that one entity includes or incorporates a building as a notable component or characteristic.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68753590819094fd70ed35d8cedf |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.