Triple
T37043598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combat Logistics Regiment 25 |
E916846
|
entity |
| Predicate | higherEchelonType |
P121884
|
FINISHED |
| Object | Marine Logistics Group |
—
|
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 Logistics Group | Statement: [Combat Logistics Regiment 25, higherEchelonType, Marine Logistics Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherEchelonType Context triple: [Combat Logistics Regiment 25, higherEchelonType, Marine Logistics Group]
-
A.
higherTierAuthority
Indicates that one entity holds a superior or higher-ranking level of authority or control over another entity.
-
B.
upperLevels
chosen
Indicates that one entity occupies or corresponds to higher levels, tiers, or hierarchical positions relative to another entity.
-
C.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
D.
higherFormationRole
Indicates that an entity serves in a specific role or function within a larger, higher-level organizational formation.
-
E.
higherTierAlternative
Indicates that one option serves as a superior or more advanced alternative to another within a tiered structure.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:14 p.m.