Triple
T29654268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terran |
E750225
|
entity |
| Predicate | coreInfantryUnit |
P157207
|
FINISHED |
| Object | Marine |
—
|
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: Marine | Statement: [Terran, coreInfantryUnit, Marine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreInfantryUnit Context triple: [Terran, coreInfantryUnit, Marine]
-
A.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
-
B.
heavyAssaultUnit
Indicates a military or combat unit that is equipped and intended to perform high-damage, front-line assault operations, typically with heavy armor or weaponry.
-
C.
isAboutMilitaryUnit
Indicates that something (such as a document, statement, or resource) concerns, discusses, or pertains to a specific military unit.
-
D.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
E.
isCombatUnit
chosen
Indicates that an entity functions as a unit specifically designated and equipped to engage in combat operations.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f269b908190a8a5f65bac23f083 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.