Triple
T33550830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sticky & Sweet Tour |
E859326
|
entity |
| Predicate | closedOnDate |
P185344
|
FINISHED |
| Object | 2009-09-02 |
—
|
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: 2009-09-02 | Statement: [Sticky & Sweet Tour, closedOnDate, 2009-09-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedOnDate Context triple: [Sticky & Sweet Tour, closedOnDate, 2009-09-02]
-
A.
closureTime
Indicates the time at which an entity, event, or process is formally closed, ended, or no longer available.
-
B.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
-
C.
closedAgainst
Indicates that an entity has been closed or shut in opposition to, or as a barrier against, another entity.
-
D.
closedIn
Indicates that one entity is enclosed, contained, or surrounded within the boundaries or limits defined by another entity.
-
E.
closedAs
Indicates that one entity has been brought to an end, resolved, or made no longer active as a result of another entity or action.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 1, 2026, 1:39 a.m.