Triple
T3922837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gila Cliff Dwellings (core archeological area) |
E93200
|
entity |
| Predicate | roofingTechnique |
P625
|
FINISHED |
| Object | timber and brush roofs over masonry walls |
—
|
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: timber and brush roofs over masonry walls | Statement: [Gila Cliff Dwellings (core archeological area), roofingTechnique, timber and brush roofs over masonry walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofingTechnique Context triple: [Gila Cliff Dwellings (core archeological area), roofingTechnique, timber and brush roofs over masonry walls]
-
A.
roofFunction
Indicates the functional role or purpose that a roof serves in relation to the structure it covers.
-
B.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
C.
roofLevel
Indicates the vertical level or story of a building at which the roof is located or begins.
-
D.
roofMaterialOriginal
Indicates the material that was originally used to construct the roof of a structure.
-
E.
constructionMethod
chosen
Indicates the technique or process by which something is built, assembled, or created.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed7c2c848190a6d62e2df9b942d4 |
completed | March 9, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.