Triple
T1843296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Striker Eureka |
E41226
|
entity |
| Predicate | tacticalRole |
P5004
|
FINISHED |
| Object | frontline Jaeger |
—
|
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: frontline Jaeger | Statement: [Striker Eureka, tacticalRole, frontline Jaeger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticalRole Context triple: [Striker Eureka, tacticalRole, frontline Jaeger]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
C.
tacticalReputation
Indicates the perceived level of skill, reliability, or effectiveness an entity has in planning and executing tactics within a given context.
-
D.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
E.
militaryFunction
chosen
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.