Triple
T36315152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monasterboice |
E894168
|
entity |
| Predicate | materialOfCrosses |
P185125
|
FINISHED |
| Object | sandstone |
—
|
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: sandstone | Statement: [Monasterboice, materialOfCrosses, sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialOfCrosses Context triple: [Monasterboice, materialOfCrosses, sandstone]
-
A.
tinctureOfCrosses
Indicates a heraldic design in which a field or charge is patterned or strewn with multiple small crosses as a repeated motif.
-
B.
crossesIn
Indicates that one entity passes over or through the path, boundary, or area occupied by another entity, intersecting its space or trajectory.
-
C.
numberOfNotchesOnCrosier
Indicates the relationship that specifies how many notches are present on a given crosier.
-
D.
featuresCrossShape
Indicates that something has a form, pattern, or configuration resembling a cross shape.
-
E.
crossesTo
Indicates that one entity moves or extends from one side or area to another, passing over or through some boundary or intervening space.
- F. None of above. chosen
Provenance (4 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.