Triple
T23418490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witham Shield |
E560576
|
entity |
| Predicate | edgeFeature |
P152176
|
FINISHED |
| Object | metal binding around rim |
—
|
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: metal binding around rim | Statement: [Witham Shield, edgeFeature, metal binding around rim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edgeFeature Context triple: [Witham Shield, edgeFeature, metal binding around rim]
-
A.
edgeType
Indicates the specific kind or category of connection that exists between two related entities.
-
B.
formsEdgeOf
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
C.
edgeTreatment
Indicates a relationship where a specific method or process is applied to modify, finish, or protect the edge of an object or material.
-
D.
typicalEdge
Indicates a standard or representative connection between two entities, as opposed to a special or exceptional type of edge.
-
E.
edgeWeights
Indicates a relationship where each edge in a graph is associated with a specific numerical weight or cost.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a5438ac08190a40a3d6402794699 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:40 p.m.