Triple
T2284153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollywood North |
E51347
|
entity |
| Predicate | associatedWithWorkforce |
P36154
|
FINISHED |
| Object | local film crews in Vancouver |
—
|
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: local film crews in Vancouver | Statement: [Hollywood North, associatedWithWorkforce, local film crews in Vancouver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWorkforce Context triple: [Hollywood North, associatedWithWorkforce, local film crews in Vancouver]
-
A.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
B.
hasWorkforceType
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
C.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
associatedWithManager
Indicates that an entity has a managerial connection or relationship with a specific manager.
-
E.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2445f388190af643878145f8249 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abbe1ecb7081909c2c66da08a48ab7 |
completed | March 7, 2026, 5:56 a.m. |
Created at: March 4, 2026, 7:48 p.m.