Triple
T31253931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianyou Peak |
E796905
|
entity |
| Predicate | valleyOverlooked |
P171505
|
FINISHED |
| Object | Wuyi Mountain valleys |
—
|
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: Wuyi Mountain valleys | Statement: [Tianyou Peak, valleyOverlooked, Wuyi Mountain valleys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valleyOverlooked Context triple: [Tianyou Peak, valleyOverlooked, Wuyi Mountain valleys]
-
A.
valleyOpensToward
Indicates that a valley is oriented or slopes in the direction of a specified location or feature, effectively opening toward it.
-
B.
valleyLocation
Indicates that one entity is located in, at, or within the geographic bounds of a valley relative to another entity or context.
-
C.
valleyKnownFor
Indicates that a particular valley is widely recognized or notable for a specific feature, product, activity, or characteristic.
-
D.
traversesValley
Indicates that an entity moves through or across a valley, passing from one side or area to another.
-
E.
overlookElevation
Indicates that one entity is positioned so as to have a higher vantage point from which it looks out over the elevation or raised area of another entity.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:12 p.m.