Triple
T38610471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orin Mannon |
E934462
|
entity |
| Predicate | hasUnrequitedLoveFrom |
P26473
|
FINISHED |
| Object | Hazel Niles |
—
|
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: Hazel Niles | Statement: [Orin Mannon, hasUnrequitedLoveFrom, Hazel Niles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnrequitedLoveFrom Context triple: [Orin Mannon, hasUnrequitedLoveFrom, Hazel Niles]
-
A.
hasFictionalRomanticInterest
Indicates that one entity is portrayed as having a romantic attraction or interest toward another entity within a fictional context.
-
B.
formerRomanticInterest
Indicates that one entity previously had a romantic relationship or attraction toward another entity, but that romantic connection has since ended.
-
C.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
D.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
E.
hasRomanticTensionWith
chosen
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:32 p.m.