Triple
T5992418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Loman |
E133381
|
entity |
| Predicate | romanticBehavior |
P52462
|
FINISHED |
| Object | pursues multiple women |
—
|
LITERAL FINISHED |
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: pursues multiple women | Statement: [Happy Loman, romanticBehavior, pursues multiple women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticBehavior Context triple: [Happy Loman, romanticBehavior, pursues multiple women]
-
A.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
B.
loveInterest
Indicates that one entity is the romantic object of affection or attraction for another entity.
-
C.
romanticReputation
chosen
Indicates how an entity is perceived or regarded by others in the context of romantic behavior, history, or involvement.
-
D.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
E.
romanceObstructedBy
Indicates that a romantic relationship or potential romance is being hindered, blocked, or prevented by some opposing factor or circumstance.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e8fd030819095a4f3b3d425ec21 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.