Triple
T35116110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucifer |
E1013440
|
entity |
| Predicate | followedByNetwork |
P198558
|
FINISHED |
| Object | Netflix |
—
|
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: Netflix | Statement: [Lucifer, followedByNetwork, Netflix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByNetwork Context triple: [Lucifer, followedByNetwork, Netflix]
-
A.
followedNetworkForSeries
Indicates that one entity has chosen to follow or subscribe to a network specifically in relation to a particular series.
-
B.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
C.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
D.
endedFollowing
Indicates that one entity stopped following or subscribing to another entity after previously doing so.
-
E.
followedByPersonaOf
Indicates that one persona is configured to follow or succeed another persona in a sequence, flow, or interaction chain.
- F. None of above. chosen
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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
| PDg | Predicate description generation | batch_69fef2da7d388190a5712a5094741f18 |
completed | May 9, 2026, 8:39 a.m. |
Created at: May 3, 2026, 4:01 p.m.