Triple
T13018696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kali Konto |
E322618
|
entity |
| Predicate | meaningOfNameElement |
P24069
|
FINISHED |
| Object | Kali means river in Indonesian and Javanese |
—
|
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: Kali means river in Indonesian and Javanese | Statement: [Kali Konto, meaningOfNameElement, Kali means river in Indonesian and Javanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfNameElement Context triple: [Kali Konto, meaningOfNameElement, Kali means river in Indonesian and Javanese]
-
A.
ordinalMeaningOfName
Indicates that a name refers to an entity’s position or rank in an ordered sequence (e.g., first, second, third).
-
B.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
C.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
D.
codeNameMeaning
Indicates that one entity is the meaning, interpretation, or significance associated with another entity’s code name.
-
E.
hasGivenNameMeaning
chosen
Indicates that a given name carries a particular meaning or semantic interpretation.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ece22908190a0941e23df7c774d |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:51 p.m.