Triple
T28765127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Odd Couple: The New Generation |
E726245
|
entity |
| Predicate | isFollowUpVehicleTo |
P165562
|
FINISHED |
| Object | The Odd Couple |
—
|
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: The Odd Couple | Statement: [The Odd Couple: The New Generation, isFollowUpVehicleTo, The Odd Couple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFollowUpVehicleTo Context triple: [The Odd Couple: The New Generation, isFollowUpVehicleTo, The Odd Couple]
-
A.
isFollowUpToSingle
Indicates that one event, message, or action directly continues or responds to a single specific prior event, message, or action.
-
B.
followsVehicle
Indicates that one vehicle is moving behind and in the same direction as another vehicle, maintaining a following position.
-
C.
intendedForVehicle
Indicates that something is designed, meant, or suitable to be used with or by a particular vehicle.
-
D.
parentVehicle
Indicates that one vehicle serves as the primary or containing vehicle from which another vehicle is derived, owned, or hierarchically related.
-
E.
relatedVehicle
Indicates that there exists an associated or connected vehicle that has a relevant relationship to the primary entity.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:13 a.m.