Triple
T28832479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honghe Hani Rice Terraces |
E728086
|
entity |
| Predicate | hasComponentArea |
P8351
|
FINISHED |
| Object | Yuanyang terraces |
—
|
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: Yuanyang terraces | Statement: [Honghe Hani Rice Terraces, hasComponentArea, Yuanyang terraces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentArea Context triple: [Honghe Hani Rice Terraces, hasComponentArea, Yuanyang terraces]
-
A.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
B.
hasComponentTerritory
chosen
Indicates that one territory is a constituent or subordinate part of a larger, encompassing territory.
-
C.
hasSourceAreaOn
Indicates that something originates from or is derived from a specified area or region.
-
D.
hasIntermediateArea
Indicates that there exists an area or region that lies between or connects two other areas in the relationship.
-
E.
hasDisplayArea
Indicates that an entity includes or is associated with a specific physical or virtual area used for displaying content or items.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: April 28, 2026, 6:38 a.m.