Triple
T29579361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commandos Marine |
E753531
|
entity |
| Predicate | specializationOfCommando de Montfort |
P71511
|
FINISHED |
| Object | support and heavy weapons |
—
|
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: support and heavy weapons | Statement: [Commandos Marine, specializationOfCommando de Montfort, support and heavy weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specializationOfCommando de Montfort Context triple: [Commandos Marine, specializationOfCommando de Montfort, support and heavy weapons]
-
A.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
-
B.
escortCommander
Indicates that one entity serves as the commanding officer responsible for leading or overseeing an escort force or mission involving another entity.
-
C.
unitSpecialization
chosen
Indicates that one unit is a specialized or more specific version of another unit within a hierarchical or categorical relationship.
-
D.
tacticalOfficer
Indicates that an entity serves in the role or capacity of a tactical officer in relation to another entity or organization.
-
E.
playedAsReturnSpecialistFor
Indicates that an entity served in the role of a return specialist for a particular team or organization.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 6:05 p.m.