Triple
T4141965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross of Nails |
E89290
|
entity |
| Predicate | materialOrigin |
P53073
|
FINISHED |
| Object | roof timbers of medieval Coventry Cathedral |
—
|
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: roof timbers of medieval Coventry Cathedral | Statement: [Cross of Nails, materialOrigin, roof timbers of medieval Coventry Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialOrigin Context triple: [Cross of Nails, materialOrigin, roof timbers of medieval Coventry Cathedral]
-
A.
materialSource
chosen
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
B.
hasSourceMaterial
Indicates that something is derived from, based on, or created using a particular source material.
-
C.
countryOfOrigin
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
D.
sourceMaterialType
Indicates the type or category of material from which something originates or is derived.
-
E.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.