Triple
T1198316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edge of Tomorrow |
E25717
|
entity |
| Predicate | hasSequelInDevelopment |
P25727
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Edge of Tomorrow, hasSequelInDevelopment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSequelInDevelopment Context triple: [Edge of Tomorrow, hasSequelInDevelopment, yes]
-
A.
hasSequel
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
-
B.
hasSequelNumber
Indicates that an entity is followed by another work in a series identified by a specific sequential number.
-
C.
laterSeriesYear
Indicates that one entity is a series whose release or production year is later than that of another related series.
-
D.
laterProducedBy
Indicates that something is produced or created by an entity at a later time than some referenced or implied production event.
-
E.
sequelReleaseYear
Indicates the calendar year in which a sequel to an original work is released.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9c013c8190822d44d465d60fdb |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:46 p.m.