Triple
T37159480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kodak Carousel pitch |
E920605
|
entity |
| Predicate | clientInScene |
P102598
|
FINISHED |
| Object | Kodak executives |
—
|
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: Kodak executives | Statement: [Kodak Carousel pitch, clientInScene, Kodak executives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientInScene Context triple: [Kodak Carousel pitch, clientInScene, Kodak executives]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
clientFor
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
-
C.
clientScope
Indicates that one entity defines or limits the scope, permissions, or accessible resources available to a client in a given context.
-
D.
scenePresence
chosen
Indicates that an entity is present or appears within a particular scene or context.
-
E.
clientServiceModel
Indicates a relationship where a particular service model is provided, managed, or applied for a given client.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.