Triple
T6129008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Posehn |
E136661
|
entity |
| Predicate | notableInterest |
P34707
|
FINISHED |
| Object | heavy metal 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: heavy metal music | Statement: [Brian Posehn, notableInterest, heavy metal music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInterest Context triple: [Brian Posehn, notableInterest, heavy metal music]
-
A.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
C.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
-
D.
subjectNotableFor
chosen
Indicates that the subject is especially recognized or distinguished for a particular attribute, achievement, role, or characteristic.
-
E.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c4c8570819096dc87f0de2a9887 |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c049fa905c8190b99eda54e9771b0b |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:15 p.m.