Triple
T20224754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chartres-style labyrinth |
E495347
|
entity |
| Predicate | hasMaterialInOriginal |
P46735
|
FINISHED |
| Object | stone inlay |
—
|
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 inlay | Statement: [Chartres-style labyrinth, hasMaterialInOriginal, stone inlay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialInOriginal Context triple: [Chartres-style labyrinth, hasMaterialInOriginal, stone inlay]
-
A.
hasOriginalPart
Indicates that an entity includes a component or segment that is part of its initial, original composition.
-
B.
originalMaterialFor
Indicates that one entity serves as the source or basis material from which another entity is derived, adapted, or created.
-
C.
hasSourceMaterial
chosen
Indicates that something is derived from, based on, or created using a particular source material.
-
D.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
E.
containsNewMaterial
Indicates that one entity includes or incorporates material that is newly created or not previously existing within another entity or context.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd8f1948190adbb947a7870bb43 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.