Triple
T22135289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandbach Crosses |
E547009
|
entity |
| Predicate | carvedWith |
P49005
|
FINISHED |
| Object | interlace ornament |
—
|
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: interlace ornament | Statement: [Sandbach Crosses, carvedWith, interlace ornament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carvedWith Context triple: [Sandbach Crosses, carvedWith, interlace ornament]
-
A.
carvedInto
Indicates that one entity has been shaped, cut, or sculpted so that it takes the form or likeness of another entity.
-
B.
carvedOutOf
Indicates that one entity has been physically shaped, cut, or formed from the material of another entity.
-
C.
carvedBy
Indicates that one entity has been shaped, cut, or sculpted from a material by another entity through a carving process.
-
D.
carvedAt
Indicates that an object or material was carved at a specific location or during a specific time.
-
E.
hasCarving
chosen
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b9ee54819081141c4f28e1211a |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.