Triple
T37012126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joanna Dark |
E915977
|
entity |
| Predicate | hasRebootAppearance |
P197255
|
FINISHED |
| Object | Perfect Dark (reboot) |
E2206426
|
NE 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: Perfect Dark (reboot) | Statement: [Joanna Dark, hasRebootAppearance, Perfect Dark (reboot)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRebootAppearance Context triple: [Joanna Dark, hasRebootAppearance, Perfect Dark (reboot)]
-
A.
hasRebootElement
chosen
Indicates that one entity includes, involves, or is associated with an element that triggers or represents a reboot of another entity or system.
-
B.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
C.
rebootAnnounced
Indicates that an official announcement has been made that a system, service, or process will be rebooted.
-
D.
rebootedOnNetwork
Indicates that a device or system was rebooted while connected to, or as part of operations on, a specific network.
-
E.
isRebootScoreFor
Indicates that one entity represents the reboot score assigned to another entity (such as a system, application, or process).
- F. None of above.
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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402b9788e48190aded4f313d09d56a |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.