Triple
T12828710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyari Town |
E306728
|
entity |
| Predicate | establishedAsTownAdministration |
P3881
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Lyari Town, establishedAsTownAdministration, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsTownAdministration Context triple: [Lyari Town, establishedAsTownAdministration, 2001]
-
A.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
-
C.
incorporatedAsTownIn
chosen
Indicates that an entity was officially established and given legal status as a town within a specified jurisdiction.
-
D.
incorporatedAsTownship
Indicates that an area or community has been formally established and recognized as a township through a legal or governmental incorporation process.
-
E.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:34 p.m.