Triple
T31031599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pénélope |
E790741
|
entity |
| Predicate | hasWorkDistributor |
P126940
|
FINISHED |
| Object | Valoria Films |
—
|
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: Valoria Films | Statement: [Pénélope, hasWorkDistributor, Valoria Films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkDistributor Context triple: [Pénélope, hasWorkDistributor, Valoria Films]
-
A.
workDistributor
Indicates that one entity is responsible for assigning, allocating, or distributing work or tasks to others.
-
B.
hasDistributedWorkOf
Indicates that an entity has assigned, allocated, or spread a particular work, task, or workload to another entity for execution or handling.
-
C.
distributedByWork
chosen
Indicates that a work (such as a film, book, or other creative product) is distributed or made available to the public by a particular distributor or organization.
-
D.
hasWorker
Indicates that one entity employs, utilizes, or is associated with another entity in the role of a worker.
-
E.
distributesOn
Indicates that one entity allocates, spreads, or apportions something across or onto another entity or set of 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 29, 2026, 8:59 p.m.