Triple
T37665208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End rod |
E937804
|
entity |
| Predicate | hasHitbox |
P200600
|
FINISHED |
| Object | thin rod shape |
—
|
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: thin rod shape | Statement: [End rod, hasHitbox, thin rod shape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHitbox Context triple: [End rod, hasHitbox, thin rod shape]
-
A.
hasNotableHit
Indicates that an entity is associated with a particularly successful, famous, or widely recognized work, performance, or achievement.
-
B.
hitboxSizeComparedToZombie
Indicates how the size of an entity’s hitbox compares to that of a standard zombie.
-
C.
isMajorHitIn
Indicates that a work (such as a song, film, or product) achieved major commercial success or popularity within a specified market, region, or context.
-
D.
collidesWith
Indicates that two entities come into contact with each other in space, typically implying an impact or physical intersection of their paths or volumes.
-
E.
hitOver
Indicates that one entity strikes or impacts another entity by moving over or across it.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
| PDg | Predicate description generation | batch_69ff9a24996c8190ba2c5345d317cbdb |
completed | May 9, 2026, 8:33 p.m. |
Created at: May 3, 2026, 4:18 p.m.