Triple
T21502851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Engelman |
E530522
|
entity |
| Predicate | roleInBlade |
P144641
|
FINISHED |
| Object | producer |
—
|
LITERAL FINISHED |
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: producer | Statement: [Robert Engelman, roleInBlade, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBlade Context triple: [Robert Engelman, roleInBlade, producer]
-
A.
roleInBladeII
Indicates that an entity has a specific role or participation in the movie "Blade II."
-
B.
roleOnVoyager
Indicates the specific position, duty, or function an entity holds in relation to the Voyager mission or project.
-
C.
roleInReact
Indicates that an entity participates in a reaction with a specified functional or contextual role (e.g., reactant, product, catalyst, or regulator).
-
D.
roleInBun
Indicates that an entity has a specific functional or contextual role within a particular bundle, grouping, or composite structure.
-
E.
roleOnPern
Indicates the specific function, position, or duty an entity holds within the context of Pern.
- F. None of above. chosen
Provenance (4 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea5deb388190a89a1f94285b7e55 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:24 p.m.