Triple
T24132474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Du Pont, Georgia |
E597990
|
entity |
| Predicate | isHistoricRailroadCommunity |
P28401
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Du Pont, Georgia, isHistoricRailroadCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricRailroadCommunity Context triple: [Du Pont, Georgia, isHistoricRailroadCommunity, true]
-
A.
hasRailroadHistory
chosen
Indicates that an entity is associated with, involved in, or notable for historical events, operations, or developments related to railroads.
-
B.
hasRailroadHistoryWith
Indicates a historical relationship or connection between entities involving railroads, such as shared development, operation, or significant events in railway history.
-
C.
hasCommunityRailDesignation
Indicates that a rail service, line, or station has been officially designated as part of a community rail initiative or program.
-
D.
formerRailroad
Indicates that an entity was previously a railroad but no longer functions as one.
-
E.
followsFormerRailroad
Indicates that something is aligned with or traces the route of a former railroad line.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df78b6f08190809fc154110fa201 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:25 p.m.