Triple
T25407232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mule Shoe salient |
E636591
|
entity |
| Predicate | frontLineType |
P135152
|
FINISHED |
| Object | salient in defensive line |
—
|
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: salient in defensive line | Statement: [Mule Shoe salient, frontLineType, salient in defensive line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontLineType Context triple: [Mule Shoe salient, frontLineType, salient in defensive line]
-
A.
frontlineType
chosen
Indicates the specific role or category of a position, unit, or activity that is directly engaged at the primary point of action or conflict.
-
B.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
C.
frontLineFeature
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
-
D.
frontLineService
Indicates that an entity provides direct, first-contact service or support to customers, clients, or the public.
-
E.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b00b10308190a7029652f6921e5d |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:52 p.m.