Triple
T17379897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCX MMXVI World Tour |
E422536
|
entity |
| Predicate | returnFromHiatus |
P107414
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [DCX MMXVI World Tour, returnFromHiatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnFromHiatus Context triple: [DCX MMXVI World Tour, returnFromHiatus, yes]
-
A.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
B.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
C.
returnedToActivity
chosen
Indicates that an entity has resumed a previously paused, stopped, or inactive activity or state.
-
D.
resumedIn
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
E.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a8559748190844c506f6f9230d4 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.