Triple
T18710532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 Private Defense Contractors |
E457496
|
entity |
| Predicate | roleInTheVoices |
P132382
|
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: [1984 Private Defense Contractors, roleInTheVoices, production company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheVoices Context triple: [1984 Private Defense Contractors, roleInTheVoices, production company]
-
A.
voiceActingRoleIn
Indicates that an entity performs a voice acting role in a specified work or production.
-
B.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
-
C.
voiceActingRole
Indicates that one entity performs the voice acting for a character or role in a work associated with the other entity.
-
D.
roleInRhyme
Indicates the specific function or part an entity plays within a rhyme, such as a character, object, or structural element of the rhyming text.
-
E.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671b34508190b6180f7d6ad50a58 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:50 a.m.