Triple
T6474288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of El Caney |
E146030
|
entity |
| Predicate | artilleryUsed |
P53761
|
FINISHED |
| Object | U.S. field artillery |
—
|
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: U.S. field artillery | Statement: [Battle of El Caney, artilleryUsed, U.S. field artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artilleryUsed Context triple: [Battle of El Caney, artilleryUsed, U.S. field artillery]
-
A.
artilleryUsedIn
chosen
Indicates that a particular piece or type of artillery is employed or deployed in a specific event, operation, or context.
-
B.
artilleryUsedBy
Indicates that a particular artillery asset is operated or employed by a specified user, such as a military unit, organization, or country.
-
C.
artilleryUsedFor
Indicates that artillery is employed or utilized for a particular purpose, function, or objective.
-
D.
hasArtilleryUse
Indicates that one entity employs, operates, or makes use of artillery in relation to another entity or context.
-
E.
artilleryType
Indicates the specific category or kind of artillery associated with an entity or event.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a32c0188190bcb3c35fc1d796a6 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:50 p.m.