Triple
T35755218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harasta |
E1033425
|
entity |
| Predicate | partOfSubdistrict |
P202626
|
FINISHED |
| Object | Harasta Subdistrict |
—
|
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: Harasta Subdistrict | Statement: [Harasta, partOfSubdistrict, Harasta Subdistrict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfSubdistrict Context triple: [Harasta, partOfSubdistrict, Harasta Subdistrict]
-
A.
subdistrictOf
Indicates that one administrative subdistrict is geographically and politically contained within, and is a part of, a larger district.
-
B.
subdistrictIn
Indicates that one administrative subdistrict is geographically or jurisdictionally contained within a larger district or region.
-
C.
partOfCountrySubdivision
Indicates that one geographic or administrative unit is contained within and forms a component part of a larger country subdivision.
-
D.
partOfPrefecture
Indicates that one entity is a subdivision or component that belongs administratively or geographically to a given prefecture.
-
E.
subdivisionOfName
Indicates that the given name is the name of a larger administrative or territorial unit of which the subject entity is a subdivision.
- F. None of above. chosen
Provenance (4 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
| PDg | Predicate description generation | batch_6a00a22d837081909f19d1078c4fedad |
completed | May 10, 2026, 3:20 p.m. |
Created at: May 3, 2026, 4:06 p.m.