Triple
T8238195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Electrical and Mechanical Engineers |
E192463
|
entity |
| Predicate | hasEmblemFeature |
P8639
|
FINISHED |
| Object | horse rearing over globe and lightning bolt |
—
|
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: horse rearing over globe and lightning bolt | Statement: [Royal Electrical and Mechanical Engineers, hasEmblemFeature, horse rearing over globe and lightning bolt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmblemFeature Context triple: [Royal Electrical and Mechanical Engineers, hasEmblemFeature, horse rearing over globe and lightning bolt]
-
A.
hasEmblemElement
Indicates that an emblem includes or features a specific element as one of its components.
-
B.
hasEmblemColor
Indicates that an emblem possesses or is characterized by a specific color.
-
C.
emblemFeatures
chosen
Indicates that an emblem includes or displays specific visual elements or characteristics.
-
D.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
-
E.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783a8cf48190bf85394fd3bd79e2 |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.