Triple
T25524564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thums Up |
E639741
|
entity |
| Predicate | isPositionedAgainst |
P75206
|
FINISHED |
| Object | Coca-Cola |
—
|
NE NERFINISHED |
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: Coca-Cola | Statement: [Thums Up, isPositionedAgainst, Coca-Cola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPositionedAgainst Context triple: [Thums Up, isPositionedAgainst, Coca-Cola]
-
A.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
B.
isPositionedAs
Indicates that one entity is placed or arranged in a specific spatial or conceptual position relative to another.
-
C.
positionOpposed
chosen
Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
-
D.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
E.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f85e975c8190bdadf34f099f3614 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 3:09 p.m.