Triple
T29201406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phalgu River |
E740282
|
entity |
| Predicate | hasSandBed |
P87904
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Phalgu River, hasSandBed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSandBed Context triple: [Phalgu River, hasSandBed, yes]
-
A.
hasSand
Indicates that something contains, is covered with, or is characterized by the presence of sand.
-
B.
hasSandColor
Indicates that one entity possesses or exhibits the sand-like color of another entity or color value.
-
C.
hasRiverBedType
Indicates the type or classification of the riverbed associated with a given river or watercourse.
-
D.
hasBedMaterial
chosen
Indicates that one entity has, contains, or is characterized by a particular bed material (e.g., the substance forming the base or bedding of that entity).
-
E.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 12:06 p.m.