Triple
T25187063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaylon primary fleet |
E630744
|
entity |
| Predicate | offenseRole |
P78138
|
FINISHED |
| Object | invasion of enemy space |
—
|
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: invasion of enemy space | Statement: [Kaylon primary fleet, offenseRole, invasion of enemy space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offenseRole Context triple: [Kaylon primary fleet, offenseRole, invasion of enemy space]
-
A.
offense
Indicates that one entity commits, causes, or is responsible for a violation, wrongdoing, or rule-breaking act against another entity or governing norms.
-
B.
playsRoleInOffense
chosen
Indicates that an entity performs a specific function or position within an offensive strategy or system.
-
C.
offensiveCharacteristic
Indicates that one entity possesses a trait, behavior, or quality that is considered insulting, disrespectful, or likely to cause offense to another entity or group.
-
D.
offenseNicknamed
Indicates that an offensive unit, team, or strategy is commonly referred to by a particular nickname.
-
E.
defensiveRole
Indicates that an entity serves a protective or guarding function 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0aeb588190b3ee13a6c031c223 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:44 p.m.