Triple
T30011142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inowrocław County |
E762462
|
entity |
| Predicate | establishedAsCountyInCurrentForm |
P179501
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Inowrocław County, establishedAsCountyInCurrentForm, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsCountyInCurrentForm Context triple: [Inowrocław County, establishedAsCountyInCurrentForm, 1999]
-
A.
unifiedAsCountyInYear
Indicates that multiple areas or jurisdictions were merged into a single county in the specified year.
-
B.
hasFormerCounty
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
C.
hasCurrentCounty
Indicates that an entity is currently located within, administered by, or associated with a specific county.
-
D.
hasConsolidatedCityCountySince
Indicates that a city and county have been formally consolidated into a single unified government entity starting from a specified point in time.
-
E.
hasCountyEquivalentStatus
Indicates that an entity holds an administrative or legal status equivalent to that of a county within a given jurisdiction.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 29, 2026, 6:44 p.m.