Triple
T2319311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mount Longdon |
E51139
|
entity |
| Predicate | supportingArm |
P32832
|
FINISHED |
| Object | naval gunfire support |
—
|
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: naval gunfire support | Statement: [Battle of Mount Longdon, supportingArm, naval gunfire support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportingArm Context triple: [Battle of Mount Longdon, supportingArm, naval gunfire support]
-
A.
supportingArms
chosen
Indicates that one entity provides military or tactical support, such as firepower or cover, to assist another entity’s operations.
-
B.
armType
Indicates the specific kind or configuration of an arm associated with an entity.
-
C.
isForwardArmOf
Indicates that one object functions as the front or leading arm/extension of another object in a given structure or system.
-
D.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
E.
hasArms
Indicates that an entity possesses arms as physical appendages.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.