Triple
T30639542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lock In |
E779935
|
entity |
| Predicate | featuresFictionalDisease |
P115956
|
FINISHED |
| Object | Haden's syndrome |
—
|
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: Haden's syndrome | Statement: [Lock In, featuresFictionalDisease, Haden's syndrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFictionalDisease Context triple: [Lock In, featuresFictionalDisease, Haden's syndrome]
-
A.
featuresFictionalVirus
Indicates that a work includes or depicts a fictional virus as part of its content or storyline.
-
B.
fictionalDisease
Indicates that an entity is associated with, afflicted by, or otherwise characterized by a disease that is imaginary or does not exist in reality.
-
C.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
D.
featuresFictionalElement
chosen
Indicates that one entity includes, presents, or incorporates a fictional element (such as an imaginary character, place, object, or concept) as part of its content or composition.
-
E.
featuresFictionalForm
Indicates that one entity includes, presents, or incorporates a fictional representation or version of 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: April 29, 2026, 8:29 p.m.