Triple
T29125310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liúyáng |
E738208
|
entity |
| Predicate | correspondsToCityInProvince |
P20236
|
FINISHED |
| Object | Hunan |
—
|
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: Hunan | Statement: [Liúyáng, correspondsToCityInProvince, Hunan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToCityInProvince Context triple: [Liúyáng, correspondsToCityInProvince, Hunan]
-
A.
associatedWithProvinceCapital
Indicates that an entity has a relationship or connection to the capital city of a specific province.
-
B.
isInProvince
chosen
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
C.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
D.
comprisesProvince
Indicates that a larger territorial or administrative unit is made up of, or includes within its boundaries, a specific province.
-
E.
provinceOf
Indicates that one administrative region functions as a province belonging to or governed by a larger territorial or political entity.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 11:28 a.m.