Triple
T2022547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MonsterVerse films |
E44135
|
entity |
| Predicate | chronologyStartYear |
P10338
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [MonsterVerse films, chronologyStartYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyStartYear Context triple: [MonsterVerse films, chronologyStartYear, 2014]
-
A.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
B.
beganInYear
chosen
Indicates that an event, process, or state started in a specific calendar year.
-
C.
originYear
Indicates the year in which something first originated, was created, or began.
-
D.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
E.
inscriptionYearOfFirstElements
Indicates the year in which the first elements of something (such as a site, object, or collection) were officially inscribed or recorded in a designated register or list.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8efbe148190901d3650aa60408a |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.