Triple
T29130612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Battalion 10th Marines |
E738363
|
entity |
| Predicate | hasBattalionEchelon |
P109891
|
FINISHED |
| Object | battalion-level command |
—
|
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: battalion-level command | Statement: [3rd Battalion 10th Marines, hasBattalionEchelon, battalion-level command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattalionEchelon Context triple: [3rd Battalion 10th Marines, hasBattalionEchelon, battalion-level command]
-
A.
hasBattalion
Indicates that one entity possesses, commands, or is organizationally assigned a specific battalion.
-
B.
isBattalionEquivalent
Indicates that one military unit has a size, role, or organizational status equivalent to that of a battalion.
-
C.
hasBattalionStructure
chosen
Indicates that an entity is organized into or associated with a battalion-level military structure.
-
D.
hasBattalionType
Indicates that an entity (such as a military unit) is associated with or classified by a specific type of battalion.
-
E.
hasBattalionNumber
Indicates that an entity (such as a military unit) is associated with a specific battalion number identifier.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 11:31 a.m.