Triple
T10596467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Marine Infantry Battalion |
E250125
|
entity |
| Predicate | positionInBattle |
P94843
|
FINISHED |
| Object | defensive positions on Mount Tumbledown |
—
|
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: defensive positions on Mount Tumbledown | Statement: [5th Marine Infantry Battalion, positionInBattle, defensive positions on Mount Tumbledown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInBattle Context triple: [5th Marine Infantry Battalion, positionInBattle, defensive positions on Mount Tumbledown]
-
A.
positionOnTactics
Indicates the stance or viewpoint an entity holds regarding a particular tactic or set of tactics.
-
B.
allyInBattle
Indicates that two or more entities cooperate on the same side as partners during a specific battle or combat situation.
-
C.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
positionInLineup
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
- F. None of above. chosen
Provenance (4 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278dacc4819089b759744f100e5f |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.