Triple
T31253930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianyou Peak |
E796905
|
entity |
| Predicate | riverOverlooked |
P155526
|
FINISHED |
| Object | Jiuqu Stream |
—
|
NE NERFINISHED |
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: Jiuqu Stream | Statement: [Tianyou Peak, riverOverlooked, Jiuqu Stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverOverlooked Context triple: [Tianyou Peak, riverOverlooked, Jiuqu Stream]
-
A.
riverPanorama
chosen
Indicates a wide, scenic view or visual representation that prominently features a river and its surrounding landscape.
-
B.
overWater
Indicates that one entity is located above or passes across a body of water, without being in direct contact with the water itself.
-
C.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
D.
riverineLocation
Indicates that something is located in, along, or directly associated with a river or river system.
-
E.
riverGhat
Indicates a relationship where a location serves as a river ghat, i.e., a stepped or designated access point to a river used for activities such as bathing, rituals, or boarding boats.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 9:12 p.m.