Triple
T587109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Combat Engineer Battalion |
E15180
|
entity |
| Predicate | serviceBranchRole |
P11687
|
FINISHED |
| Object | ground combat element support |
—
|
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: ground combat element support | Statement: [1st Combat Engineer Battalion, serviceBranchRole, ground combat element support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchRole Context triple: [1st Combat Engineer Battalion, serviceBranchRole, ground combat element support]
-
A.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
B.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
C.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
D.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
E.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9bf0cc8190a145ccd6fc501349 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494ca68448190a516b9c3525d8916 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.