Triple
T31088530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strange Tales #115 |
E792315
|
entity |
| Predicate | backupFeature |
P165207
|
FINISHED |
| Object | Doctor Strange story |
—
|
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: Doctor Strange story | Statement: [Strange Tales #115, backupFeature, Doctor Strange story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupFeature Context triple: [Strange Tales #115, backupFeature, Doctor Strange story]
-
A.
backupFeatureIn
chosen
Indicates that one feature serves as a backup or fallback for another feature within a given context or system.
-
B.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
C.
backupControlMode
Indicates that one entity serves as a fallback or secondary control mechanism for another when the primary control mode is unavailable or fails.
-
D.
backsUp
Indicates that one entity provides support, reinforcement, or confirmation for another entity’s actions, statements, or position.
-
E.
backupScope
Indicates the extent or range of data, resources, or components that are included in a backup operation.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.