Triple
T31443869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qiongwen |
E802137
|
entity |
| Predicate | hasRegionSpecificName |
P40944
|
FINISHED |
| Object | Qiongwen (瓊文 or 琼文) in Chinese |
—
|
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: Qiongwen (瓊文 or 琼文) in Chinese | Statement: [Qiongwen, hasRegionSpecificName, Qiongwen (瓊文 or 琼文) in Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionSpecificName Context triple: [Qiongwen, hasRegionSpecificName, Qiongwen (瓊文 or 琼文) in Chinese]
-
A.
hasRegionalName
chosen
Indicates that an entity is known by a specific name or designation within a particular region or locality.
-
B.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
C.
hasRegionalHolidayName
Indicates that a regional holiday is associated with a specific name or designation used to refer to it.
-
D.
countrySpecificName
Indicates that an entity has a name or label that is specific to, or used within, a particular country.
-
E.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0160834e388190908591b300954d29 |
completed | May 11, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a01602a83408190a11d754bdc7da0e9 |
completed | May 11, 2026, 4:50 a.m. |
Created at: April 30, 2026, 9:08 p.m.