Triple
T24434001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cabin Creek |
E616074
|
entity |
| Predicate | supplyTrainSize |
P156122
|
FINISHED |
| Object | approximately 300 wagons |
—
|
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: approximately 300 wagons | Statement: [Battle of Cabin Creek, supplyTrainSize, approximately 300 wagons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supplyTrainSize Context triple: [Battle of Cabin Creek, supplyTrainSize, approximately 300 wagons]
-
A.
supplyBy
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
-
B.
supplySituation
Indicates a relationship where one entity provides or makes available needed resources, goods, or services to another under specific conditions or circumstances.
-
C.
supplyMode
Indicates the manner or method by which something is provided, delivered, or made available.
-
D.
suppliedTroopsTo
Indicates that one entity provided military personnel or forces to another entity.
-
E.
logisticsSupportFrom
Indicates that one entity provides logistical assistance, resources, or services to another entity.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297855fd08190904eedd2666d9622 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.