Triple
T31305967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunan linguistic area |
E798336
|
entity |
| Predicate | hasPeripheralRegion |
P285
|
FINISHED |
| Object | border areas with Guangxi |
—
|
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: border areas with Guangxi | Statement: [Hunan linguistic area, hasPeripheralRegion, border areas with Guangxi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeripheralRegion Context triple: [Hunan linguistic area, hasPeripheralRegion, border areas with Guangxi]
-
A.
hasPeripheralPattern
Indicates that one entity exhibits or is characterized by a pattern located at or toward the periphery or outer boundary of another entity.
-
B.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
isPeripheralFor
Indicates that one entity functions as a peripheral or auxiliary component in relation to another primary system or device.
-
D.
hasRingRegion
Indicates that one entity possesses or includes a ring-shaped region as part of its structure or spatial extent.
-
E.
hasRegionBehind
Indicates that one region is spatially located behind another region relative to a given viewpoint or reference frame.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 29, 2026, 9:14 p.m.