Triple
T4440495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAGA hat |
E95758
|
entity |
| Predicate | writtenOnFront |
P10347
|
FINISHED |
| Object | Make America Great Again |
—
|
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: Make America Great Again | Statement: [MAGA hat, writtenOnFront, Make America Great Again]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenOnFront Context triple: [MAGA hat, writtenOnFront, Make America Great Again]
-
A.
usedOnFront
Indicates that something is applied, displayed, or positioned on the front side or front-facing part of another object or entity.
-
B.
areWrittenOn
chosen
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
C.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
D.
frontDesignSameAsBack
Indicates that the design on the front side of an object is identical to the design on its back side.
-
E.
partOfFront
Indicates that one entity constitutes a component or section located at the front portion of another entity.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355ac05e081908411089c05fc36bd |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.