Triple
T30936090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jon Landau |
E788126
|
entity |
| Predicate | co-produced |
P24872
|
FINISHED |
| Object | Titanic |
—
|
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: Titanic | Statement: [Jon Landau, co-produced, Titanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: co-produced Context triple: [Jon Landau, co-produced, Titanic]
-
A.
coProduced
chosen
Indicates that two or more entities jointly produced or created a work, project, or product together.
-
B.
coProductionType
Indicates the specific nature or category of a collaborative production relationship between multiple producing entities.
-
C.
associatedProduction
Indicates that there is a related or connected production (such as a work, performance, or manufacturing process) linked to the subject entity.
-
D.
coExecutiveProducerOf
Indicates a person who shares the role and responsibilities of an executive producer for a particular production or project.
-
E.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692e5069c81908013503ba8d065d7 |
completed | May 3, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:52 p.m.