Triple
T35533091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Plains 2 |
E1026856
|
entity |
| Predicate | containsEnemy |
P189050
|
FINISHED |
| Object | Buzzy Beetle |
—
|
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: Buzzy Beetle | Statement: [Donut Plains 2, containsEnemy, Buzzy Beetle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEnemy Context triple: [Donut Plains 2, containsEnemy, Buzzy Beetle]
-
A.
hasEnemies
Indicates that one entity is in an antagonistic or hostile relationship with another, considering them an enemy.
-
B.
hasUniqueEnemy
Indicates that an entity has exactly one distinct enemy with whom it is in an antagonistic relationship.
-
C.
enemyPresence
chosen
Indicates the presence of hostile or adversarial entities in relation to a specified entity or location.
-
D.
hasEnemiesTrait
Indicates that an entity possesses a characteristic or quality specifically related to having enemies.
-
E.
enemyCharacterIn
Indicates that a character is located within or present inside an enemy-controlled area, zone, 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00c07b302081908bf9755f8fdbc36e |
completed | May 10, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_6a00bfffb168819084b65804d601896d |
completed | May 10, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:04 p.m.