Triple
T2198769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let the Right One In |
E50438
|
entity |
| Predicate | remakeLanguage |
P36901
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Let the Right One In, remakeLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remakeLanguage Context triple: [Let the Right One In, remakeLanguage, English]
-
A.
languageShift
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
-
B.
lexifierLanguage
Indicates that one language serves as the primary source or base language from which the core vocabulary and structure of another language, typically a pidgin or creole, are derived.
-
C.
hasRemake
Indicates that one work is a new version or recreation of an earlier existing work.
-
D.
formerLanguage
Indicates that one entity was previously the language of another entity but is no longer in that role.
-
E.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf7b65cc8190bcc5a5c52b90f33b |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf35c994819088a093c412931de4 |
completed | March 7, 2026, 6:01 a.m. |
Created at: March 4, 2026, 7:46 p.m.