Triple
T31655516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Mosby |
E807847
|
entity |
| Predicate | laterRomanticOutcome |
P153136
|
FINISHED |
| Object | reunites with Robin Scherbatsky in series finale |
—
|
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: reunites with Robin Scherbatsky in series finale | Statement: [Ted Mosby, laterRomanticOutcome, reunites with Robin Scherbatsky in series finale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRomanticOutcome Context triple: [Ted Mosby, laterRomanticOutcome, reunites with Robin Scherbatsky in series finale]
-
A.
romanticOutcome
Indicates that a romantic relationship or interaction between entities results in a particular outcome, such as success, failure, or change in status.
-
B.
romanticSubplotCentral
Indicates that a romantic subplot is a primary, driving element of the narrative rather than a minor or peripheral thread.
-
C.
laterLoves
chosen
Indicates that one entity comes to love another at a later time than some referenced point or event.
-
D.
hasRomanticSubplot
Indicates that a work includes a secondary storyline centered on a romantic relationship between characters.
-
E.
romanceType
Indicates the specific kind or category of romantic relationship that exists between the related entities.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: April 30, 2026, 10:55 p.m.