Triple
T33608453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meridian Campaign |
E860921
|
entity |
| Predicate | railroadsDestroyed |
P176953
|
FINISHED |
| Object | Mobile and Ohio Railroad segments |
—
|
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: Mobile and Ohio Railroad segments | Statement: [Meridian Campaign, railroadsDestroyed, Mobile and Ohio Railroad segments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadsDestroyed Context triple: [Meridian Campaign, railroadsDestroyed, Mobile and Ohio Railroad segments]
-
A.
tramwayDestroyedBy
Indicates that a tramway was damaged or rendered unusable as a direct result of an action or event caused by another entity.
-
B.
unionWagonsLostApprox
Indicates that an approximate number of wagons belonging to a union has been lost.
-
C.
railroad
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
-
D.
buildingsDestroyed
Indicates that one or more buildings have been damaged to the point of destruction as a result of some event or action.
-
E.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:41 a.m.