Triple
T7240894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Pictures Studios lot |
E155350
|
entity |
| Predicate | centralHubFor |
P2958
|
FINISHED |
| Object | Sony motion picture operations |
—
|
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: Sony motion picture operations | Statement: [Sony Pictures Studios lot, centralHubFor, Sony motion picture operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralHubFor Context triple: [Sony Pictures Studios lot, centralHubFor, Sony motion picture operations]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
C.
primaryHubFor
chosen
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:55 p.m.