Triple
T30088968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of Nine Villages |
E764674
|
entity |
| Predicate | hasMainValley |
P86468
|
FINISHED |
| Object | Shuzheng Valley |
—
|
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: Shuzheng Valley | Statement: [Valley of Nine Villages, hasMainValley, Shuzheng Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainValley Context triple: [Valley of Nine Villages, hasMainValley, Shuzheng Valley]
-
A.
hasValley
Indicates that one entity contains, features, or is characterized by the presence of a valley associated with the other entity.
-
B.
primaryValley
chosen
Indicates that a valley is the main or most significant valley associated with a given geographic feature or region.
-
C.
hasRoadAlongValley
Indicates that a road runs along or follows the course of a valley.
-
D.
hasHeadOfValleyNear
Indicates that the head (uppermost part) of a valley is located near a specified reference feature or entity.
-
E.
hasRiverValley
Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: April 29, 2026, 7:05 p.m.