Triple
T29249152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phường Cự Khối |
E741512
|
entity |
| Predicate | hasParentDistrict |
P152090
|
FINISHED |
| Object | Long Biên District |
—
|
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: Long Biên District | Statement: [Phường Cự Khối, hasParentDistrict, Long Biên District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentDistrict Context triple: [Phường Cự Khối, hasParentDistrict, Long Biên District]
-
A.
hasParentDistrictHeadquarters
Indicates that an administrative district has a specific location designated as its parent (or main) district headquarters.
-
B.
hasRelatedDistrict
chosen
Indicates that one entity is associated with, linked to, or falls within the scope of a particular district.
-
C.
hasParentCounty
Indicates that a given county is administratively or geographically contained within, and subordinate to, a specified parent county.
-
D.
hasDistrictPart
Indicates that one administrative or geographic entity includes another entity as a district-level subdivision or component.
-
E.
isMainDistrictOf
Indicates that a district serves as the primary or central administrative district of a specified larger area or jurisdiction.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 12:33 p.m.