Triple
T27758465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiger Shark |
E701394
|
entity |
| Predicate | preCodeHollywood |
P64463
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tiger Shark, preCodeHollywood, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preCodeHollywood Context triple: [Tiger Shark, preCodeHollywood, true]
-
A.
madeInHollywood
Indicates that something was produced or created within Hollywood, typically referring to the Hollywood film or entertainment industry.
-
B.
isPreCodeFilm
chosen
Indicates that a film was produced and released before the enforcement of the Hollywood Production Code (Hays Code), and thus belongs to the pre-Code era.
-
C.
isScriptedEntertainment
Indicates that the entertainment content is pre-planned and follows a written script rather than being spontaneous or unscripted.
-
D.
popularFilmIndustry
Indicates that an entity has a widely recognized and well-liked film industry that attracts significant audience interest and attention.
-
E.
developerOfWorkAppearingIn
Indicates that one entity is the creator or developer of a work in which another entity appears or is featured.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637636910819087e8bb5ecb026a9a |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:25 p.m.