Triple
T34556399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Johns River estuary |
E887215
|
entity |
| Predicate | facesEnvironmentalPressure |
P77335
|
FINISHED |
| Object | urban development |
—
|
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: urban development | Statement: [St. Johns River estuary, facesEnvironmentalPressure, urban development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesEnvironmentalPressure Context triple: [St. Johns River estuary, facesEnvironmentalPressure, urban development]
-
A.
environmentalResponse
Indicates how an entity reacts or adapts to changes or conditions in its surrounding environment.
-
B.
environmentalFactor
chosen
Indicates that one entity functions as an environmental influence or condition that affects another entity or process.
-
C.
surfacePressure
Indicates the pressure exerted by a fluid (such as air or water) on the surface of an object or body.
-
D.
facedPressureFrom
Indicates that one entity experienced coercion, influence, or stress exerted by another entity to act or decide in a certain way.
-
E.
environmentalCondition
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.