Triple
T33209847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas Easter |
E850121
|
entity |
| Predicate | hasFictionalPartner |
P192977
|
FINISHED |
| Object | Marlee |
—
|
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: Marlee | Statement: [Nicholas Easter, hasFictionalPartner, Marlee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalPartner Context triple: [Nicholas Easter, hasFictionalPartner, Marlee]
-
A.
hasHumanPartnerCharacter
Indicates that an entity is associated with a partner character who is human.
-
B.
hasFictionalRomanticInterest
chosen
Indicates that one entity is portrayed as having a romantic attraction or interest toward another entity within a fictional context.
-
C.
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.
-
D.
romanticPartnerInSeries
Indicates that one character is portrayed as a romantic partner of another character within the context of a specific series or narrative.
-
E.
hasFictionalCompanion
Indicates that one entity has another entity as its fictional companion, typically within a narrative or imaginative context.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 1, 2026, 1:30 a.m.