Triple
T28487621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REME |
E720874
|
entity |
| Predicate | wearsCapBadge |
P9510
|
FINISHED |
| Object | Royal Electrical and Mechanical Engineers cap badge |
—
|
NE NERFINISHED |
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 Electrical and Mechanical Engineers cap badge | Statement: [REME, wearsCapBadge, Royal Electrical and Mechanical Engineers cap badge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearsCapBadge Context triple: [REME, wearsCapBadge, Royal Electrical and Mechanical Engineers cap badge]
-
A.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
B.
wearsCapLogo
Indicates that an entity is wearing a cap that displays a specific logo.
-
C.
hasInsigniaWornBy
chosen
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
D.
woreCaptainArmbandFor
Indicates that one entity served as captain by wearing the captain’s armband for another entity (typically a team or side) during a match or event.
-
E.
authorizedHeadgear
Indicates that a particular item of headgear is officially permitted or approved for use in a given context or by a specific authority.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f1072108190b52d8c1665e3b071 |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:59 a.m.