Triple
T23554437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Island Light |
E578142
|
entity |
| Predicate | nrhpListingReason |
P17397
|
FINISHED |
| Object | maritime history |
—
|
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: maritime history | Statement: [Long Island Light, nrhpListingReason, maritime history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nrhpListingReason Context triple: [Long Island Light, nrhpListingReason, maritime history]
-
A.
NRHPListingReason
chosen
Indicates the reason or justification for a property's inclusion in the National Register of Historic Places (NRHP).
-
B.
NRHPListingNearby
Indicates that one entity is located close to another entity that is listed on the National Register of Historic Places (NRHP).
-
C.
NRHPListingName
Indicates that a place or property has a specific official name under its listing in the National Register of Historic Places (NRHP).
-
D.
heritageDesignationReason
Indicates the reason or justification for which something has been granted a particular heritage designation.
-
E.
nationalRegisterOfHistoricPlacesListing
Indicates that an entity is officially listed in the National Register of Historic Places as a recognized historic property or site.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed17fc881908b45dcde14790d42 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:12 p.m.