Triple
T37938387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calculon |
E946410
|
entity |
| Predicate | productionCompanyInUniverse |
P115000
|
FINISHED |
| Object | Channel √2 |
—
|
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: Channel √2 | Statement: [Calculon, productionCompanyInUniverse, Channel √2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionCompanyInUniverse Context triple: [Calculon, productionCompanyInUniverse, Channel √2]
-
A.
productionCompanyInFiction
chosen
Indicates that a company is depicted as a production company within a fictional work or universe.
-
B.
productionCompanyOfWork
Indicates that a company is responsible for producing a particular creative work (such as a film, TV show, or similar production).
-
C.
coProductionCompany
Indicates a company that collaborates with one or more other companies in the joint production of a work or project.
-
D.
productionCompanyOfOrigin
Indicates the company that originally produced or was primarily responsible for creating a given work or product.
-
E.
filmProductionCompanyOfAppearance
Indicates the company responsible for producing the film in which a particular appearance occurs.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 3, 2026, 4:20 p.m.