Triple
T21747668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budweiser (U.S. Navy SEAL insignia) |
E536828
|
entity |
| Predicate | positionOnUniform |
P6852
|
FINISHED |
| Object | left breast |
—
|
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: left breast | Statement: [Budweiser (U.S. Navy SEAL insignia), positionOnUniform, left breast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnUniform Context triple: [Budweiser (U.S. Navy SEAL insignia), positionOnUniform, left breast]
-
A.
locationOnUniform
chosen
Indicates that a specific location or marking appears on a uniform.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionOnBehavior
Indicates the stance, attitude, or viewpoint one entity holds regarding another entity’s behavior or conduct.
-
D.
positionOnUnion
Indicates the stance or viewpoint an entity holds regarding a union, such as support, opposition, or neutrality.
-
E.
positionUse
Indicates how a particular position or role is utilized or functionally applied within a given context.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a77e19c81909bf26f96aa41a7ce |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.