Triple
T11658901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creeper |
E277074
|
entity |
| Predicate | hostility |
P21197
|
FINISHED |
| Object | hostile toward players |
—
|
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: hostile toward players | Statement: [Creeper, hostility, hostile toward players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostility Context triple: [Creeper, hostility, hostile toward players]
-
A.
belligerentAgainst
chosen
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
B.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
C.
belligerentInterest
Indicates that an entity has a hostile, aggressive, or conflict-seeking attitude or stake toward another entity or situation.
-
D.
harborsResentmentToward
Indicates that one entity holds ongoing bitterness, anger, or ill will directed at another entity.
-
E.
offense
Indicates that one entity commits, causes, or is responsible for a violation, wrongdoing, or rule-breaking act against another entity or governing norms.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.