Triple
T26871646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice League Mortal |
E676623
|
entity |
| Predicate | cancellationStage |
P110290
|
FINISHED |
| Object | pre-production |
—
|
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: pre-production | Statement: [Justice League Mortal, cancellationStage, pre-production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cancellationStage Context triple: [Justice League Mortal, cancellationStage, pre-production]
-
A.
cancellation
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
-
B.
developmentPhaseAtCancellation
chosen
Indicates the specific stage of development a project or product had reached at the time it was cancelled.
-
C.
cancellationAnnouncedOn
Indicates that the cancellation of something (e.g., an event, service, or agreement) was publicly announced on a specific date or time.
-
D.
canceledBy
Indicates that an action, event, or agreement was annulled or called off by a specific entity.
-
E.
canceledAfter
Indicates that one event or action was canceled at a point in time occurring after another specified event or action.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:32 a.m.