Triple
T5190526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape May Seashore Lines |
E117140
|
entity |
| Predicate | heritageOperation |
P50902
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cape May Seashore Lines, heritageOperation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageOperation Context triple: [Cape May Seashore Lines, heritageOperation, yes]
-
A.
isHeritageOperation
chosen
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.
-
B.
heritageOperator
Indicates that an entity operates, manages, or runs a heritage-related site, service, or asset.
-
C.
heritageFunction
Indicates the role, use, or purpose that a heritage asset or element serves within its cultural, historical, or social context.
-
D.
heritageComponent
Indicates that one entity forms a constituent or contributing part of another entity’s cultural or historical heritage.
-
E.
heritageField
Indicates that there is an association between an entity and a specific field, domain, or area related to cultural or historical heritage.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79ebbfd081909a19b903c227fc1f |
completed | March 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.