Triple
T27255973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Cay |
E687615
|
entity |
| Predicate | environmentQuality |
P122731
|
FINISHED |
| Object | pristine |
—
|
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: pristine | Statement: [South Cay, environmentQuality, pristine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentQuality Context triple: [South Cay, environmentQuality, pristine]
-
A.
hasEnvironmentalQuality
chosen
Indicates that something possesses a particular environmental characteristic, condition, or attribute.
-
B.
environmentAuthority
Indicates that an entity has official regulatory or supervisory power over environmental matters affecting another entity or area.
-
C.
environmentRole
Indicates the functional role or influence that one entity has within or upon a particular environment or environmental context.
-
D.
environmentalIssue
Indicates that something is a problem or concern related to the natural environment, such as harm, risk, or negative impact on ecosystems or resources.
-
E.
environmentalFactor
Indicates that one entity functions as an environmental influence or condition that affects another entity or process.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 10:49 a.m.