Triple
T30354727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asiri traditional architecture |
E772111
|
entity |
| Predicate | builtUsingTechnique |
P3047
|
FINISHED |
| Object | load-bearing masonry |
—
|
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: load-bearing masonry | Statement: [Asiri traditional architecture, builtUsingTechnique, load-bearing masonry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtUsingTechnique Context triple: [Asiri traditional architecture, builtUsingTechnique, load-bearing masonry]
-
A.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
B.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
C.
constructionTechniqueComparedTo
Indicates a relationship where one construction technique is evaluated or contrasted against another in terms of method, quality, efficiency, or other relevant criteria.
-
D.
builtThrough
Indicates that something was created, developed, or achieved by means of a specified method, process, or intermediary.
-
E.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823e27d88190af8342b01f9876e8 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.