Triple
T3557497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Eastleigh |
E75253
|
entity |
| Predicate | createdAsDistrict |
P50586
|
FINISHED |
| Object | 1 April 1974 |
—
|
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: 1 April 1974 | Statement: [Borough of Eastleigh, createdAsDistrict, 1 April 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAsDistrict Context triple: [Borough of Eastleigh, createdAsDistrict, 1 April 1974]
-
A.
formerDistrict
Indicates that one entity previously served as a district of another entity but no longer holds that status.
-
B.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
C.
federalDistrictCreatedBy
Indicates that a federal district was established or brought into existence through the action, decision, or authority of a specified creator (such as a government body, law, or decree).
-
D.
createdForJurisdiction
Indicates that something was created specifically to apply within, serve, or be used by a particular legal or geographic jurisdiction.
-
E.
federalDistrictCreated
Indicates that a federal district has been formally established or brought into existence.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc086e6688190b90ae356e18b953e |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:20 p.m.