Triple
T34346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Want YOU for U.S. Army poster |
E683
|
entity |
| Predicate | visualMotive |
P463
|
FINISHED |
| Object | figure pointing at viewer |
—
|
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: figure pointing at viewer | Statement: [I Want YOU for U.S. Army poster, visualMotive, figure pointing at viewer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualMotive Context triple: [I Want YOU for U.S. Army poster, visualMotive, figure pointing at viewer]
-
A.
envisionedAs
Indicates that one entity is mentally pictured, imagined, or conceived in terms of another entity or role.
-
B.
monitors
Indicates that one entity observes, tracks, or checks the state, behavior, or performance of another entity over time.
-
C.
marketPosition
Indicates the relative standing or rank an entity holds within a specific market compared to its competitors.
-
D.
inception
Indicates the point in time or event at which something begins, originates, or is first established.
-
E.
demonstratedConcept
chosen
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a24872e4e481908567850168d65015 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.