Triple
T16779144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truman Burbank |
E407810
|
entity |
| Predicate | unknowinglyFilmedBy |
P124595
|
FINISHED |
| Object | hidden cameras |
—
|
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: hidden cameras | Statement: [Truman Burbank, unknowinglyFilmedBy, hidden cameras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unknowinglyFilmedBy Context triple: [Truman Burbank, unknowinglyFilmedBy, hidden cameras]
-
A.
wasRecordedIn
Indicates that an event, action, or piece of information was documented or captured within a specific record, medium, or recording session.
-
B.
filmedAs
Indicates that an entity was recorded or captured in a particular form, version, or role during a filming or production process.
-
C.
filmedFrom
Indicates that one entity serves as the physical or conceptual vantage point or recording source from which another entity (such as a scene, object, or event) is filmed.
-
D.
recordedForFilm
Indicates that an audio or performance was captured specifically for use in a film production.
-
E.
filmWithinFilm
Indicates that one film is depicted, referenced, or shown as existing within the narrative of another film.
- F. None of above. chosen
Provenance (4 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21401b881909bbbc7382e851a90 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.