Triple
T28024725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messy |
E707784
|
entity |
| Predicate | hasChronologicalSuccessor |
P121704
|
FINISHED |
| Object | Without You |
—
|
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: Without You | Statement: [Messy, hasChronologicalSuccessor, Without You]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChronologicalSuccessor Context triple: [Messy, hasChronologicalSuccessor, Without You]
-
A.
isSuccessorTo
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
-
B.
chronologicallySucceededBy
chosen
Indicates that one event or state occurs later in time than, and thus follows, another.
-
C.
hasOnlineSuccessor
Indicates that one entity is the direct online or digital successor of another, typically replacing or continuing its function in an online context.
-
D.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
E.
hasModernSuccessor
Indicates that an entity is followed or replaced by another entity that serves as its modern equivalent or continuation.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 8:12 p.m.