Triple
T17039592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Share a Coke |
E413409
|
entity |
| Predicate | replacedElement |
P29646
|
FINISHED |
| Object | Coca-Cola logo on bottles |
—
|
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: Coca-Cola logo on bottles | Statement: [Share a Coke, replacedElement, Coca-Cola logo on bottles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedElement Context triple: [Share a Coke, replacedElement, Coca-Cola logo on bottles]
-
A.
replacedEntity
Indicates that one entity has been substituted for, or taken the place of, another entity in a given context.
-
B.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacedDocument
Indicates that one document has been superseded or substituted by another document.
-
D.
replacedClass
Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
-
E.
replacedAfterEvent
Indicates that one entity takes the place of another entity following a specified event or occurrence.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f5844c819097eade4a2b42ab91 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.