Triple
T34801001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Series watch |
E1003217
|
entity |
| Predicate | customReplacedBy |
P29646
|
FINISHED |
| Object | World Series ring |
—
|
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: World Series ring | Statement: [World Series watch, customReplacedBy, World Series ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customReplacedBy Context triple: [World Series watch, customReplacedBy, World Series ring]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
D.
indirectlyReplacedBy
Indicates that one entity has been superseded or taken over by another entity through one or more intermediate replacements, rather than by a direct, immediate substitution.
-
E.
replacedOnPlatformBy
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.