Triple
T30639593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head On |
E779936
|
entity |
| Predicate | hasFictionalDisease |
P143817
|
FINISHED |
| Object | Haden's syndrome |
—
|
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: Haden's syndrome | Statement: [Head On, hasFictionalDisease, Haden's syndrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalDisease Context triple: [Head On, hasFictionalDisease, Haden's syndrome]
-
A.
fictionalDisease
chosen
Indicates that an entity is associated with, afflicted by, or otherwise characterized by a disease that is imaginary or does not exist in reality.
-
B.
hasEponymousDisease
Indicates that an entity (typically a person) has a disease named after them.
-
C.
hasFictionalSpecialization
Indicates that an entity’s area of focus, expertise, or role is within a fictional or imaginative domain rather than a real-world specialization.
-
D.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
E.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
- 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_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 29, 2026, 8:29 p.m.