Triple
T20791599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Monterey Pass |
E511790
|
entity |
| Predicate | capturedWagons |
P141556
|
FINISHED |
| Object | over 250 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: over 250 wagons | Statement: [Battle of Monterey Pass, capturedWagons, over 250 wagons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedWagons Context triple: [Battle of Monterey Pass, capturedWagons, over 250 wagons]
-
A.
carriagesInvolved
Indicates that specific carriages are participants in, or affected by, the referenced event or situation.
-
B.
railCarries
Indicates that a rail or railway system transports or conveys a specified entity from one place to another.
-
C.
laterRollingStock
Indicates that one piece of rolling stock comes into use or service at a later time than another piece of rolling stock.
-
D.
ownedRollingStock
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
-
E.
railwayCarriageUsedFor
Indicates that a railway carriage is employed or designated for a particular purpose, function, or type of use.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2910d488190bc4be37512effc86 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:38 p.m.