Triple
T33776402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venus (film universe) |
E865533
|
entity |
| Predicate | hasOriginWork |
P45645
|
FINISHED |
| Object | "Venus" (film) |
—
|
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: "Venus" (film) | Statement: [Venus (film universe), hasOriginWork, "Venus" (film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginWork Context triple: [Venus (film universe), hasOriginWork, "Venus" (film)]
-
A.
hasOriginalWorkSetting
Indicates that an entity is associated with the setting or context in which the original work or source material takes place.
-
B.
originatedInWorkBy
Indicates that something was created, derived, or first appeared within a particular work produced by a specific creator.
-
C.
hasSourceWork
chosen
Indicates that something originates from, is derived from, or is based on a particular source work.
-
D.
originatesFromWork
Indicates that something has its source, derivation, or creation in a particular work (such as a document, artwork, or publication).
-
E.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 1, 2026, 1:45 a.m.