Triple
T18719106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headquarters and Service Company, 26th Marines |
E457720
|
entity |
| Predicate | regimentalLevel |
P18686
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Headquarters and Service Company, 26th Marines, regimentalLevel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalLevel Context triple: [Headquarters and Service Company, 26th Marines, regimentalLevel, yes]
-
A.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
B.
militaryFormationLevel
chosen
Indicates the hierarchical level or scale of a military formation within an armed forces organizational structure.
-
C.
raisedRegiment
Indicates that an entity organized, formed, or brought into existence a specific military regiment.
-
D.
regimentalTitle
Indicates the formal or official title assigned to a military regiment within an organizational or historical context.
-
E.
numberOfRegimentsInvolved
Indicates the total count of regiments that participated in or were involved in a specified event or action.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab90adc81909f3b4aabb6d5a707 |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.