Triple
T13351627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Pictures |
E318081
|
entity |
| Predicate | workLanguageAssociatedWith |
P18404
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Sky Pictures, workLanguageAssociatedWith, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workLanguageAssociatedWith Context triple: [Sky Pictures, workLanguageAssociatedWith, English]
-
A.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
B.
isWorkingLanguageOf
chosen
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
C.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
D.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
E.
languageAssociation
Indicates an association or relationship between entities based on a language they use, represent, or are linked to.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8c2f1c819094f0970f35f18afa |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6fd8bc819086dddb6f376efa57 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:32 p.m.