Triple
T28877460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yichang counties |
E732310
|
entity |
| Predicate | areGovernedFrom |
P98499
|
FINISHED |
| Object | Yichang city |
—
|
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: Yichang city | Statement: [Yichang counties, areGovernedFrom, Yichang city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areGovernedFrom Context triple: [Yichang counties, areGovernedFrom, Yichang city]
-
A.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
B.
areGovernedBy
chosen
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
C.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
D.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
E.
governedTraditionallyBy
Indicates that one entity has historically exercised customary or long-established governing authority over another 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4cb030819097b892710baa7d88 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:39 a.m.