Triple
T34494377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jennifer Parker (Back to the Future film series) |
E885558
|
entity |
| Predicate | spouseInAlternateTimelineOf |
P195977
|
FINISHED |
| Object | Marty McFly |
—
|
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: Marty McFly | Statement: [Jennifer Parker (Back to the Future film series), spouseInAlternateTimelineOf, Marty McFly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseInAlternateTimelineOf Context triple: [Jennifer Parker (Back to the Future film series), spouseInAlternateTimelineOf, Marty McFly]
-
A.
spouseFate
Indicates that one person’s fate, status, or outcome is defined specifically in relation to their spouse.
-
B.
possiblySpouse
Indicates that two entities may be spouses, reflecting an uncertain or hypothesized marital relationship between them.
-
C.
spouseInQuestion
Indicates that the referenced person is the spouse of the primary entity being discussed or queried.
-
D.
spouseIn
Indicates that one entity is the spouse (married partner) of another entity within a specified context or grouping.
-
E.
subjectSpouseAtTime
Indicates that the subject is married to a specified spouse during a particular time period.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
| PDg | Predicate description generation | batch_69fdfbae00e481908a2e4558b9dee07e |
completed | May 8, 2026, 3:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.