Triple
T9407448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Service Ensign |
E226621
|
entity |
| Predicate | badgeVariesBy |
P89006
|
FINISHED |
| Object | government department |
—
|
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: government department | Statement: [Government Service Ensign, badgeVariesBy, government department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: badgeVariesBy Context triple: [Government Service Ensign, badgeVariesBy, government department]
-
A.
badge
Indicates that one entity confers, displays, or is associated with a symbolic mark or emblem representing status, achievement, role, or affiliation in relation to another entity.
-
B.
badgeText
Indicates that a visual badge or label is associated with an entity, displaying specific text content.
-
C.
badgeEnamelColor
Indicates the color of the enamel portion of a badge.
-
D.
badgeSymbolMeaning
Indicates that a badge’s symbol represents or conveys a particular meaning or significance.
-
E.
badgeEngineeredFrom
Indicates that a badge is derived, created, or generated based on another underlying source, design, or system.
- F. None of above. chosen
Provenance (4 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c3fc988190ac34cc9e09f8ebfc |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca9d07eb08190866eb15333386dfa |
completed | April 1, 2026, 5:14 a.m. |
Created at: March 30, 2026, 7:47 p.m.