Triple
T35191395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principal Rosalie Mullins |
E1016127
|
entity |
| Predicate | hasHiddenInterestIn |
P152666
|
FINISHED |
| Object | rock music |
—
|
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: rock music | Statement: [Principal Rosalie Mullins, hasHiddenInterestIn, rock music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHiddenInterestIn Context triple: [Principal Rosalie Mullins, hasHiddenInterestIn, rock music]
-
A.
hasHumanInterest
Indicates that something is of particular relevance, appeal, or concern to people, often engaging their emotions, curiosity, or personal experiences.
-
B.
hasOverlappingInterestsFrom
Indicates that one entity shares some, but not necessarily all, interests in common with another entity, such that their sets of interests partially overlap.
-
C.
hasInterestType
Indicates that an entity is associated with a specific category or type of interest it holds or is concerned with.
-
D.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
E.
interestMayBe
chosen
Indicates that one entity potentially has an interest in, or may be interested in, another entity or subject.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:02 p.m.