Triple
T38383471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maja of the Hårga community |
E893816
|
entity |
| Predicate | romanticallyTargets |
P121646
|
FINISHED |
| Object | Christian Hughes |
—
|
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: Christian Hughes | Statement: [Maja of the Hårga community, romanticallyTargets, Christian Hughes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticallyTargets Context triple: [Maja of the Hårga community, romanticallyTargets, Christian Hughes]
-
A.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
B.
romanticallyIdealizedBy
Indicates that one entity is viewed or portrayed by another as a perfect or ideal romantic partner, often in an unrealistic or idealized way.
-
C.
romanticPattern
Indicates a recurring style, tendency, or structure in how romantic relationships or attractions develop or are expressed between entities.
-
D.
romanticIdeal
Indicates that one entity is regarded by another as an ideal or preferred model in a romantic context.
-
E.
romanticAssociation
chosen
Indicates a romantic relationship or involvement exists between the associated 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.