Triple
T25541681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchild |
E640189
|
entity |
| Predicate | isFollowedInSingleChronologyBy |
P125022
|
FINISHED |
| Object | Kisses on the Wind |
—
|
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: Kisses on the Wind | Statement: [Manchild, isFollowedInSingleChronologyBy, Kisses on the Wind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFollowedInSingleChronologyBy Context triple: [Manchild, isFollowedInSingleChronologyBy, Kisses on the Wind]
-
A.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
B.
hasChronologyRelation
Indicates a temporal ordering relationship between entities, specifying how one relates to another in time (e.g., before, after, or overlapping).
-
C.
followsIn
chosen
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
D.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
E.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f895278881909c376fc06b290c56 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:26 p.m.