Triple
T26183568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamar River |
E654754
|
entity |
| Predicate | isEcologicalCorridor |
P160024
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tamar River, isEcologicalCorridor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEcologicalCorridor Context triple: [Tamar River, isEcologicalCorridor, true]
-
A.
isEcologicalZone
Indicates that one entity functions as, or is classified as, an ecological zone in relation to another entity.
-
B.
isEcologicalRefugeWithin
Indicates that one ecological refuge is spatially contained within the boundaries of another specified area or refuge.
-
C.
isStrategicCorridor
Indicates that a route, passage, or area serves as a critical pathway for movement, access, or control, giving it significant strategic importance.
-
D.
hasEcology
Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
-
E.
hasMajorEcosystemNearby
Indicates that one entity is located close enough to another entity that the latter significantly influences or characterizes the surrounding ecosystem.
- F. None of above. chosen
Provenance (4 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c72995481909d7e33abb0df2298 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:41 p.m.