Triple
T36957616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Schabbs |
E914227
|
entity |
| Predicate | healthAttribute |
P186802
|
FINISHED |
| Object | high hit points compared to regular enemies |
—
|
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: high hit points compared to regular enemies | Statement: [Dr. Schabbs, healthAttribute, high hit points compared to regular enemies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthAttribute Context triple: [Dr. Schabbs, healthAttribute, high hit points compared to regular enemies]
-
A.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
B.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of an entity.
-
C.
heartAttribute
Indicates a relationship where a specific attribute or quality is associated with the heart, such as its condition, characteristic, or state.
-
D.
healthHabit
Indicates a relationship where an entity regularly engages in a behavior or practice that affects its health or well-being.
-
E.
coreAttribute
Indicates that one attribute is a fundamental, defining, or essential property of another entity.
- F. None of above. chosen
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.