Triple
T31165785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catch Us If You Can |
E794463
|
entity |
| Predicate | filmUsageType |
P126403
|
FINISHED |
| Object | theme song |
—
|
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: theme song | Statement: [Catch Us If You Can, filmUsageType, theme song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmUsageType Context triple: [Catch Us If You Can, filmUsageType, theme song]
-
A.
hasTypeOfUseInFilm
chosen
Indicates that something is associated with a specific manner or category of use within the context of a film.
-
B.
usesFilmFormat
Indicates that one entity employs or is recorded in a particular film format associated with the other entity.
-
C.
filmTypeContext
Indicates the contextual relationship between a film and its type or category within a specific classification or usage setting.
-
D.
usesFootageType
Indicates that one entity employs or incorporates a particular type or category of footage in its content or production.
-
E.
filmStockType
Indicates the specific type or category of photographic or motion picture film stock used or 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:07 p.m.