Triple
T25848876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmington and Western Railroad |
E651145
|
entity |
| Predicate | heritageOperationsBegan |
P144581
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Wilmington and Western Railroad, heritageOperationsBegan, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageOperationsBegan Context triple: [Wilmington and Western Railroad, heritageOperationsBegan, 1960s]
-
A.
heritageOperationsStart
chosen
Indicates the point in time when heritage-related operations or activities begin.
-
B.
isHeritageOperation
Indicates that an operation is designated as a heritage-related activity, typically involving the preservation, restoration, or maintenance of culturally or historically significant assets or practices.
-
C.
heritageServicesStart
Indicates the point in time when heritage-related services or activities begin.
-
D.
hasHeritageOperations
Indicates that an entity conducts or maintains operations related to heritage, such as cultural, historical, or legacy assets or activities.
-
E.
heritageOperator
Indicates that an entity operates, manages, or runs a heritage-related site, service, or asset.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 22, 2026, 7:57 a.m.