Triple
T27698177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolsa Chica State Beach |
E698353
|
entity |
| Predicate | ecosystemTypeNearby |
P141543
|
FINISHED |
| Object | coastal wetland |
—
|
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: coastal wetland | Statement: [Bolsa Chica State Beach, ecosystemTypeNearby, coastal wetland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecosystemTypeNearby Context triple: [Bolsa Chica State Beach, ecosystemTypeNearby, coastal wetland]
-
A.
hasNearbyEcosystemType
chosen
Indicates that one entity has an ecosystem of a specified type located in its immediate surrounding area.
-
B.
hasMajorEcosystemNearby
Indicates that one entity is located close enough to another entity that the latter significantly influences or characterizes the surrounding ecosystem.
-
C.
lakeTypeNearby
Indicates that one entity is located near another entity that is classified as a particular type of lake.
-
D.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
-
E.
hasNearbyWetlandRegion
Indicates that a given location or area is situated close to, or in the vicinity of, a wetland region.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a0a2788190bc17046fa79d26a6 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:55 p.m.