Triple
T3743333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Seashores |
E79750
|
entity |
| Predicate | includeFeatures |
P41649
|
FINISHED |
| Object | beaches |
—
|
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: beaches | Statement: [National Seashores, includeFeatures, beaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeFeatures Context triple: [National Seashores, includeFeatures, beaches]
-
A.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
B.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
-
C.
featuresOrchestrationBy
Indicates that something (such as a work, event, or performance) is characterized by or includes orchestration carried out by a particular agent or entity.
-
D.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
-
E.
displaysFeature
chosen
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb576b5881908515d64c71f11a16 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.