Triple
T25373015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxi County |
E632977
|
entity |
| Predicate | hasAutonomousPrefectureSeat |
P85336
|
FINISHED |
| Object | Jishou |
—
|
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: Jishou | Statement: [Luxi County, hasAutonomousPrefectureSeat, Jishou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutonomousPrefectureSeat Context triple: [Luxi County, hasAutonomousPrefectureSeat, Jishou]
-
A.
hasPrefecturalCapitalFunction
Indicates that an entity serves as the administrative capital or main governmental center of a prefecture.
-
B.
hasPrefecturalOffice
chosen
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
-
C.
isInPrefecturalCapital
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
-
D.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
-
E.
prefectureOfHeadquarters
Indicates the administrative prefecture in which an organization's headquarters is located.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:38 p.m.