Triple
T7201329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albi |
E168751
|
entity |
| Predicate | materialUsedInTraditionalArchitecture |
P1272
|
FINISHED |
| Object | red 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: red brick | Statement: [Albi, materialUsedInTraditionalArchitecture, red brick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialUsedInTraditionalArchitecture Context triple: [Albi, materialUsedInTraditionalArchitecture, red brick]
-
A.
buildingMaterialTradition
Indicates the customary or historically established use of particular materials in the construction of a building or structure.
-
B.
traditionalMaterial
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
C.
materialOfFortifications
Indicates that a specified material is used in the construction or composition of certain fortifications.
-
D.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
materialFromQuarriesUsedFor
Indicates that material extracted from quarries is used for a particular purpose, project, or object.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e94971508190bb38184c9af2fe51 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.