Triple
T33773820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio JMS |
E865457
|
entity |
| Predicate | roleInSense8 |
P202636
|
FINISHED |
| Object | production company |
—
|
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: production company | Statement: [Studio JMS, roleInSense8, production company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSense8 Context triple: [Studio JMS, roleInSense8, production company]
-
A.
roleInSyriana
Indicates that one entity has a specific role or involvement in the context of "Syriana," such as participation, function, or contribution related to it.
-
B.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
C.
roleInBabel
Indicates that an entity participates in the Babel project or system with a specific role or function.
-
D.
roleInAlienCovenant
Indicates that an entity has a role or participation in the film "Alien: Covenant."
-
E.
roleInWatchmen
Indicates that one entity has a specific role or function within the context of the work "Watchmen" in relation to the other entity.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_6a00a2f0207c81908eaaff8c2a0b3f97 |
completed | May 10, 2026, 3:23 p.m. |
Created at: May 1, 2026, 1:45 a.m.