Triple
T32371368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Słubice |
E827145
|
entity |
| Predicate | afterYearBecameSeparateTown |
P134469
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Słubice, afterYearBecameSeparateTown, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterYearBecameSeparateTown Context triple: [Słubice, afterYearBecameSeparateTown, 1945]
-
A.
wasDividedFromYear
Indicates that an entity began to be separated or partitioned starting from a specified year.
-
B.
dateOfCommunitySeparation
chosen
Indicates the date on which a community formally separated or split from another community or larger entity.
-
C.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
-
D.
partOfMunicipalitySince
Indicates that an entity has been included within and administratively belonging to a specific municipality starting from a given point in time.
-
E.
wasDividedFrom
Indicates that one entity was separated or split off from another entity, resulting in two distinct parts or groups.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 12:50 a.m.