Triple
T37661842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Player (Minecraft) |
E937734
|
entity |
| Predicate | hasHealthPoints |
P100270
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Player (Minecraft), hasHealthPoints, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthPoints Context triple: [Player (Minecraft), hasHealthPoints, 20]
-
A.
healthPointsJava
chosen
Indicates the number of health points an entity has within a Java-based context or implementation.
-
B.
hasBaseHP
Indicates that an entity possesses a specified amount of base hit points (HP) as its fundamental health value.
-
C.
hitPointsType
Indicates the category or nature of hit points an entity uses (e.g., health, shield, or other durability type) in the relationship or system.
-
D.
hasVitality
Indicates that an entity possesses a level or quality of life force, energy, or biological liveliness.
-
E.
healthPointsBedrock
Indicates the amount of health points associated with or provided by a bedrock entity or state.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:18 p.m.