Triple
T37820617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Gawain’s shield |
E942901
|
entity |
| Predicate | hasMaterialInText |
P1845
|
FINISHED |
| Object | bright and precious metal |
—
|
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: bright and precious metal | Statement: [Sir Gawain’s shield, hasMaterialInText, bright and precious metal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialInText Context triple: [Sir Gawain’s shield, hasMaterialInText, bright and precious metal]
-
A.
hasTextIn
Indicates that an entity contains or is associated with a specific piece of text within a particular context or location.
-
B.
hasMaterialResource
Indicates that an entity possesses, controls, or has access to a tangible material resource.
-
C.
hasMaterialType
chosen
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
D.
hasMaterialContext
Indicates that something is associated with, influenced by, or situated within a particular physical or material context.
-
E.
hasMaterialRole
Indicates that an entity participates in an activity or context by fulfilling a specific material-related role or function.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.