Triple
T11338082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pine District Pictures |
E268522
|
entity |
| Predicate | roleInFrancesHa |
P98582
|
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: [Pine District Pictures, roleInFrancesHa, production company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFrancesHa Context triple: [Pine District Pictures, roleInFrancesHa, production company]
-
A.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
B.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
C.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
D.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
-
E.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea008b5081908e6c6c6fc29ef936 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:33 p.m.