Triple
T16994454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox Movies |
E412276
|
entity |
| Predicate | hasProgrammingSource |
P48294
|
FINISHED |
| Object | major Hollywood studios |
—
|
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: major Hollywood studios | Statement: [Fox Movies, hasProgrammingSource, major Hollywood studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammingSource Context triple: [Fox Movies, hasProgrammingSource, major Hollywood studios]
-
A.
hasProgrammingFrom
chosen
Indicates that something derives its programming, configuration, or behavioral instructions from a specified source.
-
B.
hasProgrammingDomain
Indicates that an entity is associated with or specializes in a particular programming domain or area of software development.
-
C.
typicalProgrammingSource
Indicates that one entity is a common or standard source from which the other entity obtains programming content or code.
-
D.
hasProgrammingFocus
Indicates that something is centered on, specialized in, or primarily concerned with programming.
-
E.
hasProgrammingTheme
Indicates that something involves, is centered around, or is characterized by programming-related concepts, activities, or content.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d285f35881908c32b2f27ba7f0ac |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.