Triple
T35181675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deviant Love |
E1015866
|
entity |
| Predicate | hasProminentRoleActor |
P166850
|
FINISHED |
| Object | Micah Stock |
E322290
|
NE 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: Micah Stock | Statement: [Deviant Love, hasProminentRoleActor, Micah Stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentRoleActor Context triple: [Deviant Love, hasProminentRoleActor, Micah Stock]
-
A.
hasProminentSupportingActor
Indicates that an entity (such as a film or show) features a supporting actor whose role or recognition is notably significant within that work.
-
B.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
C.
leadRoleActor
chosen
Indicates that an actor performs a leading or principal role in a work or production.
-
D.
replacesInLeadRole
Indicates that one entity takes over or substitutes for another entity in the primary or leading role within a given context or production.
-
E.
hasPortrayedRole
Indicates that an entity has performed or depicted a specific role or character, typically in a work such as a film, play, or television show.
- F. None of above.
Provenance (4 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a036054129081909e66c5d62015e6c1 |
completed | May 12, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819ca5cf8819097d26dc19fac8730 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a035f17cbf88190acd6bdbfc9789ffb |
completed | May 12, 2026, 5:10 p.m. |
Created at: May 3, 2026, 4:02 p.m.