Triple
T14777203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garter circlet |
E347290
|
entity |
| Predicate | traditionallyEncircles |
P7850
|
FINISHED |
| Object | royal coat of arms |
—
|
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: royal coat of arms | Statement: [Garter circlet, traditionallyEncircles, royal coat of arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyEncircles Context triple: [Garter circlet, traditionallyEncircles, royal coat of arms]
-
A.
partlyEncircles
Indicates that one entity surrounds another along a substantial but incomplete portion of its boundary or perimeter.
-
B.
surrounds
chosen
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
C.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
D.
traditionAt
Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
-
E.
traditionIncludes
Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec817c39081909b08a0ffdfce9936 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.