Triple
T24266775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WarGames |
E604858
|
entity |
| Predicate | fictionalComputerFullName |
P151065
|
FINISHED |
| Object | War Operation Plan Response |
—
|
NE NERFINISHED |
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: War Operation Plan Response | Statement: [WarGames, fictionalComputerFullName, War Operation Plan Response]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalComputerFullName Context triple: [WarGames, fictionalComputerFullName, War Operation Plan Response]
-
A.
supercomputerName
chosen
Indicates that an entity has the specified name used to identify it as a supercomputer.
-
B.
fictionalNameInSeries
Indicates that a fictional character is known by a particular name within a specific narrative series or franchise.
-
C.
computerSystem
Indicates a relationship where an entity functions as or is classified as a computer system, typically comprising hardware, software, and related components that operate together.
-
D.
fictionalCorporation
Indicates that an entity is a corporation that exists only in fiction rather than in the real world.
-
E.
fictionalObject
Indicates that one entity is a fictional or imaginary object in relation to another entity.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6bfe68819084ec59235ae58ff1 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.