Triple
T16202047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ano Pedina |
E393225
|
entity |
| Predicate | materialUsedInBuildings |
P112810
|
FINISHED |
| Object | stone |
—
|
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: stone | Statement: [Ano Pedina, materialUsedInBuildings, stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialUsedInBuildings Context triple: [Ano Pedina, materialUsedInBuildings, stone]
-
A.
مادة البناء
chosen
Indicates a relationship where something serves as, or is used as, a construction material in building or structural work.
-
B.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
hasArchitecturalMaterial
Indicates that something is constructed from, incorporates, or is characterized by a particular architectural material.
-
D.
constructionUsed
Indicates that one entity was employed as a construction method, material, or component in creating or assembling another entity.
-
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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2270b84408190bfbf68f32bfc5b1a |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.