Triple
T28804083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shizhuanshan site |
E727323
|
entity |
| Predicate | isKeyLocationOf |
P18908
|
FINISHED |
| Object | Dazu Rock Carvings complex |
—
|
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: Dazu Rock Carvings complex | Statement: [Shizhuanshan site, isKeyLocationOf, Dazu Rock Carvings complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyLocationOf Context triple: [Shizhuanshan site, isKeyLocationOf, Dazu Rock Carvings complex]
-
A.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
-
B.
hasKeyLocation
chosen
Indicates that an entity possesses or is associated with a specific primary or important location relevant to it.
-
C.
isKeySiteOf
Indicates that a location serves as an important or central place for a particular event, activity, process, or function.
-
D.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
E.
isKeyRegionIn
Indicates that a region plays a central or strategically important role within a larger area, system, or context.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:28 a.m.