Triple
T5855326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiang'an District |
E130135
|
entity |
| Predicate | isAdminCenterOf |
P18611
|
FINISHED |
| Object | none |
—
|
LITERAL FINISHED |
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: none | Statement: [Jiang'an District, isAdminCenterOf, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdminCenterOf Context triple: [Jiang'an District, isAdminCenterOf, none]
-
A.
hasCentralAdministrationIn
Indicates that an organization or entity maintains its primary central administrative authority or headquarters in a specified location.
-
B.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
C.
hasRAndDCenterIn
Indicates that an entity maintains a research and development (R&D) center located in a specified place.
-
D.
managingCenter
chosen
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
-
E.
isReferralCenterFor
Indicates that one entity serves as a designated center to which other entities send or direct cases, clients, or tasks for specialized services or handling.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.