Triple
T1627225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eight Million Plus Productions |
E35172
|
entity |
| Predicate | productionRole |
P268
|
FINISHED |
| Object | co-producer of Lip Sync Battle |
—
|
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: co-producer of Lip Sync Battle | Statement: [Eight Million Plus Productions, productionRole, co-producer of Lip Sync Battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionRole Context triple: [Eight Million Plus Productions, productionRole, co-producer of Lip Sync Battle]
-
A.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
B.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
C.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
-
D.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
produces
Indicates that one entity creates, generates, or yields another entity as a result or output.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.