Triple
T33737709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Webster |
E864465
|
entity |
| Predicate | isRomanticLeadOf |
P177260
|
FINISHED |
| Object | Last Christmas |
—
|
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: Last Christmas | Statement: [Tom Webster, isRomanticLeadOf, Last Christmas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRomanticLeadOf Context triple: [Tom Webster, isRomanticLeadOf, Last Christmas]
-
A.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
B.
romanticPartnerInSeries
Indicates that one character is portrayed as a romantic partner of another character within the context of a specific series or narrative.
-
C.
romanticPartnerRealName
Indicates that the real, non-alias name of a person is associated with someone who is their romantic partner.
-
D.
romanticPartnerInSpinOff
Indicates that two characters are depicted as romantic partners specifically within a spin-off work, rather than (or in addition to) the original series.
-
E.
isFianceeOf
Indicates that one person is the engaged-to-be-married partner of another person.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb54446881909265a17685fa5e4a |
completed | May 3, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:44 a.m.