Triple
T9407439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Service Ensign |
E226621
|
entity |
| Predicate | badgePlacement |
P48677
|
FINISHED |
| Object | fly |
—
|
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: fly | Statement: [Government Service Ensign, badgePlacement, fly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: badgePlacement Context triple: [Government Service Ensign, badgePlacement, fly]
-
A.
buttonPlacement
Indicates the spatial or positional arrangement of a button relative to other elements or within a given interface or context.
-
B.
logoPlacement
chosen
Indicates the spatial or contextual position where a logo is displayed or applied in relation to another object, surface, or medium.
-
C.
badgeText
Indicates that a visual badge or label is associated with an entity, displaying specific text content.
-
D.
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.
-
E.
ribbonPosition
Indicates the spatial or ordered placement of a ribbon relative to a reference object or coordinate system.
- 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_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. |
Created at: March 30, 2026, 7:47 p.m.