Triple
T31948464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capri limestone plateau |
E815714
|
entity |
| Predicate | surfaceDrainage |
P173040
|
FINISHED |
| Object | scarce |
—
|
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: scarce | Statement: [Capri limestone plateau, surfaceDrainage, scarce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceDrainage Context triple: [Capri limestone plateau, surfaceDrainage, scarce]
-
A.
drainageBasin
Indicates the area of land where all precipitation and surface water flow are collected and drained toward a particular river, lake, or other water body.
-
B.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
C.
drainageBasinShape
Indicates the characteristic geometric form or outline of a drainage basin as defined by its boundary and flow patterns.
-
D.
drainageInfluencedBy
Indicates that the pattern, direction, or effectiveness of drainage is affected or controlled by another factor or entity.
-
E.
watershedArea
Indicates the total land area from which surface water drains into a particular water body or point in the drainage system.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:07 a.m.