Triple
T34798223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Water Management Areas of South Africa |
E1003145
|
entity |
| Predicate | hasHistoricalVersionCount |
P16369
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [National Water Management Areas of South Africa, hasHistoricalVersionCount, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalVersionCount Context triple: [National Water Management Areas of South Africa, hasHistoricalVersionCount, 19]
-
A.
hasVersionCount
chosen
Indicates the total number of distinct versions associated with a given entity.
-
B.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
-
C.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
D.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
-
E.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 3:59 p.m.