Triple
T20701023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romance on the High Seas |
E508779
|
entity |
| Predicate | basedInStudioSystem |
P60411
|
FINISHED |
| Object | Hollywood studio system era |
—
|
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: Hollywood studio system era | Statement: [Romance on the High Seas, basedInStudioSystem, Hollywood studio system era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInStudioSystem Context triple: [Romance on the High Seas, basedInStudioSystem, Hollywood studio system era]
-
A.
setInStudio
Indicates that an entity is located, placed, or takes place within a studio environment.
-
B.
hasStudio
Indicates that an entity (such as a film, game, or production) is associated with or produced by a particular studio.
-
C.
workedWithStudioSystem
chosen
Indicates that an individual has been professionally involved in or employed under a studio-based production or distribution system.
-
D.
ownedStudio
Indicates that one entity possessed ownership or controlling interest in a particular studio.
-
E.
foundedStudio
Indicates that an entity established or created a particular studio as its founder.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c18bfac08190bf80beeb3ce1951a |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:12 p.m.