Triple
T17738498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barka River |
E442787
|
entity |
| Predicate | isIntermittent |
P128808
|
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: [Barka River, isIntermittent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntermittent Context triple: [Barka River, isIntermittent, true]
-
A.
isUnstable
Indicates that the subject lacks stability or consistency, often changing, fluctuating, or failing to remain in a steady state.
-
B.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
C.
possibleInterruption
Indicates that one event, action, or process may interrupt, break into, or otherwise disrupt the continuity of another.
-
D.
hasInterference
Indicates that one entity negatively affects or obstructs the normal function, performance, or occurrence of another entity or process.
-
E.
meetsIrregularly
Indicates that two or more entities come together or interact on a non-fixed, inconsistent, or unpredictable schedule.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47aca27448190943c75e723ceefcc |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:09 a.m.