Triple
T28837761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chùa Hương |
E728230
|
entity |
| Predicate | provinceHistorically |
P45290
|
FINISHED |
| Object | Hà Tây Province |
—
|
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: Hà Tây Province | Statement: [Chùa Hương, provinceHistorically, Hà Tây Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceHistorically Context triple: [Chùa Hương, provinceHistorically, Hà Tây Province]
-
A.
regionHistory
Indicates that there exists a historical or past association between a subject and a specific geographic or administrative region.
-
B.
historicallyBasedIn
chosen
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
-
C.
governingStateInHistory
Indicates that one state historically exercised governing authority or control over another entity during a specific period in the past.
-
D.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
E.
provinceAtTime
Indicates that an entity is a province of (or belongs to the jurisdiction of) another entity during a specified time or time interval.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 28, 2026, 6:39 a.m.