Triple
T15072699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chasing the Dime |
E379918
|
entity |
| Predicate | standalone |
P92727
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chasing the Dime, standalone, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standalone Context triple: [Chasing the Dime, standalone, true]
-
A.
notStandalone
Indicates that an entity cannot exist, function, or be valid independently and must be associated with or supported by another entity.
-
B.
isStandaloneFriendly
Indicates that an entity can operate or be used effectively on its own without requiring integration or support from other entities.
-
C.
standaloneWithinSeries
Indicates that an item is part of a larger series but is intended to function independently and be understandable on its own, without requiring direct reliance on other parts of the series.
-
D.
isStandaloneWork
chosen
Indicates that a work exists independently and is not part of a larger series, collection, or multi-part work.
-
E.
wirelessStandalone
Indicates that something operates wirelessly on its own, without needing to be connected to or dependent on another device or system.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fa0570819088a97b28173154cd |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.