Triple
T26583103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanyue District |
E667129
|
entity |
| Predicate | hasFiveGreatMountainsSite |
P10602
|
FINISHED |
| Object | Mount Heng |
—
|
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: Mount Heng | Statement: [Nanyue District, hasFiveGreatMountainsSite, Mount Heng]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFiveGreatMountainsSite Context triple: [Nanyue District, hasFiveGreatMountainsSite, Mount Heng]
-
A.
hasNationalParkSite
Indicates that a location, region, or jurisdiction contains or is home to at least one designated national park site.
-
B.
hasMountain
chosen
Indicates that a location or region possesses or contains at least one mountain.
-
C.
hasSummitFacility
Indicates that one entity possesses or provides a facility or infrastructure located at the summit of another entity (such as a mountain, hill, or peak).
-
D.
hasAncestralMountain
Indicates that an entity has a specific mountain recognized as its ancestral place of origin or heritage.
-
E.
hasMultipleSummits
Indicates that an entity (such as a mountain or peak) consists of more than one distinct summit or high point.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 2:04 a.m.