Triple
T17909055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamondhead |
E447773
|
entity |
| Predicate | canCreateProjectiles |
P1454
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Diamondhead, canCreateProjectiles, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCreateProjectiles Context triple: [Diamondhead, canCreateProjectiles, Yes]
-
A.
hasProjectilePointCharacteristic
Indicates that an entity possesses a specific attribute or feature related to a projectile point (such as its form, technology, or measurable properties).
-
B.
involvesProjectile
chosen
Indicates that the action or event includes the use, presence, or motion of a projectile as a key component of the interaction between entities.
-
C.
hasCannon
Indicates that one entity is equipped with, contains, or features a cannon.
-
D.
canSpawnWith
Indicates that one entity is able to appear, be created, or originate in conjunction with another entity under the same conditions or context.
-
E.
usesCanons
Indicates that one entity employs or makes use of canons (such as rules, principles, or artillery pieces) in relation to another entity or context.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9e4c9881908bfc3a83809d6b85 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.