Triple
T8649129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuareg tent architecture |
E205053
|
entity |
| Predicate | ventilationStrategy |
P41511
|
FINISHED |
| Object | openable side panels |
—
|
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: openable side panels | Statement: [Tuareg tent architecture, ventilationStrategy, openable side panels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ventilationStrategy Context triple: [Tuareg tent architecture, ventilationStrategy, openable side panels]
-
A.
ventilationFeature
chosen
Indicates that one entity has a structural or functional role related to providing, enabling, or affecting ventilation for another entity.
-
B.
hasVentilationShafts
Indicates that one entity is equipped with or contains ventilation shafts that provide airflow or air passage.
-
C.
hasVentilationBuildings
Indicates that certain buildings are designated to provide ventilation for another structure, area, or system.
-
D.
coolingStrategy
Indicates the method or approach used to reduce or control temperature in a system or environment.
-
E.
hasFlankVents
Indicates that an entity possesses vents located on its sides or flanks.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4812b7bc8190acb40da57cad293a |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.