Triple
T23979195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardcore Henry |
E604458
|
entity |
| Predicate | shotInFormat |
P119255
|
FINISHED |
| Object | first-person perspective |
—
|
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: first-person perspective | Statement: [Hardcore Henry, shotInFormat, first-person perspective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shotInFormat Context triple: [Hardcore Henry, shotInFormat, first-person perspective]
-
A.
sensorFormat
Indicates the data encoding or representation standard used by a sensor to output its measurements.
-
B.
appearsInFilmFormat
Indicates that something is presented or occurs within a specific film format or medium of cinematic presentation.
-
C.
usesFilmFormat
Indicates that one entity employs or is recorded in a particular film format associated with the other entity.
-
D.
originallyShotOn
chosen
Indicates that a visual work was first recorded or captured using a particular original medium, format, or equipment.
-
E.
projectionFormat
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bc79688190bc98a2d57b91f5a3 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:26 p.m.