Triple
T38184200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panchagangavalli River |
E1005261
|
entity |
| Predicate | numberOfTributaryRivers |
P207631
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Panchagangavalli River, numberOfTributaryRivers, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfTributaryRivers Context triple: [Panchagangavalli River, numberOfTributaryRivers, 5]
-
A.
hasTributaries
Indicates that a watercourse receives smaller streams or rivers that flow into it as tributaries.
-
B.
tributaryRank
Indicates the relative hierarchical level or importance of a tributary within a river or drainage network.
-
C.
tributarySystemOf
Indicates that one political entity is subordinate to another, providing tribute or services in exchange for protection, recognition, or limited autonomy within a hierarchical system.
-
D.
hasNumberOfRivers
Indicates the quantitative relationship specifying how many rivers are associated with a given entity.
-
E.
tributarySystem
Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:29 p.m.