Triple
T31031597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pénélope |
E790741
|
entity |
| Predicate | hasWorkProductionCompany |
P14415
|
FINISHED |
| Object | Titanus |
—
|
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: Titanus | Statement: [Pénélope, hasWorkProductionCompany, Titanus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkProductionCompany Context triple: [Pénélope, hasWorkProductionCompany, Titanus]
-
A.
hasProductionCompany
chosen
Indicates that an entity (such as a film, show, or media work) is associated with a specific company responsible for its production.
-
B.
productionCompanyOfWork
Indicates that a company is responsible for producing a particular creative work (such as a film, TV show, or similar production).
-
C.
belongsToProductionCompany
Indicates that a media work (such as a film or TV show) is produced or owned by a specific production company.
-
D.
hasFictionalProductionCompany
Indicates that one entity is associated with or owns a production company that exists only within a fictional context.
-
E.
ownedProductionCompany
Indicates that one entity previously possessed ownership or controlling interest in a production company.
- 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_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 29, 2026, 8:59 p.m.