Triple
T21319608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wading River |
E525575
|
entity |
| Predicate | hasEcologyType |
P25102
|
FINISHED |
| Object | coastal plain ecology |
—
|
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 plain ecology | Statement: [Wading River, hasEcologyType, coastal plain ecology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcologyType Context triple: [Wading River, hasEcologyType, coastal plain ecology]
-
A.
hasEcology
chosen
Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
-
B.
containsEcologicalTypes
Indicates that one entity includes or encompasses specific ecological types or categories within it.
-
C.
hasEcologicalProcess
Indicates that one entity exhibits, participates in, or is characterized by a particular ecological process affecting its environment or ecosystem.
-
D.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
E.
hasEcologicalSite
Indicates that one entity is associated with, or located within, a particular ecological site or ecological classification unit.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ecfb7d481909cb73f95c3ddd9ed |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:38 p.m.