Triple
T35057048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abarkuh |
E1011495
|
entity |
| Predicate | buildingMaterialTraditionallyUsed |
P50559
|
FINISHED |
| Object | mud-brick |
—
|
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: mud-brick | Statement: [Abarkuh, buildingMaterialTraditionallyUsed, mud-brick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingMaterialTraditionallyUsed Context triple: [Abarkuh, buildingMaterialTraditionallyUsed, mud-brick]
-
A.
buildingMaterialTradition
Indicates the customary or historically established use of particular materials in the construction of a building or structure.
-
B.
traditionalMaterial
chosen
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
C.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
D.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
E.
traditionalUseSince
Indicates that something has been used in a traditional way starting from a specified point in time.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785d2233881909b0b1d604db44e53 |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.