Triple
T8784924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nike "Just Do It" 30th anniversary campaign |
E209019
|
entity |
| Predicate | positionedNikeAs |
P85358
|
FINISHED |
| Object | supporter of athlete activism |
—
|
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: supporter of athlete activism | Statement: [Nike "Just Do It" 30th anniversary campaign, positionedNikeAs, supporter of athlete activism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionedNikeAs Context triple: [Nike "Just Do It" 30th anniversary campaign, positionedNikeAs, supporter of athlete activism]
-
A.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
B.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
-
C.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f7441e8819081ea0ae7bc2afde7 |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:42 p.m.