Triple
T2157697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindisfarne Gospels |
E47928
|
entity |
| Predicate | dimensions |
P3633
|
FINISHED |
| Object | large-format codex |
—
|
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: large-format codex | Statement: [Lindisfarne Gospels, dimensions, large-format codex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensions Context triple: [Lindisfarne Gospels, dimensions, large-format codex]
-
A.
dimension
chosen
Indicates that one entity specifies a measurable extent or size attribute (such as length, width, height, or similar quantitative property) of another entity.
-
B.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
-
C.
dimensionCount
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
-
D.
dimensionOfComponents
Indicates that a specified dimension value is associated with, or applies to, the components of an object or system.
-
E.
dimensionDependentProperties
Indicates that certain properties or characteristics of an entity vary as a function of its dimensional attributes (such as size, length, or number of dimensions).
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe68fe0c8190beb5db003738a6e5 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.