Triple
T5245742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scots Guards |
E118453
|
entity |
| Predicate | identifyingFeature |
P37670
|
FINISHED |
| Object | plume on left side of bearskin |
—
|
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: plume on left side of bearskin | Statement: [Scots Guards, identifyingFeature, plume on left side of bearskin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifyingFeature Context triple: [Scots Guards, identifyingFeature, plume on left side of bearskin]
-
A.
helpsIdentify
Indicates a relationship where one entity serves to distinguish, recognize, or determine the identity or characteristics of another entity.
-
B.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
D.
describesCharacteristicOf
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
E.
iconicFeature
chosen
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b515edc8190a9db198d4eb1c4f6 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.