Triple
T37799603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa pod Oliwą |
E942332
|
entity |
| Predicate | hasPolishBase |
P201272
|
FINISHED |
| Object | Gdańsk |
—
|
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: Gdańsk | Statement: [Bitwa pod Oliwą, hasPolishBase, Gdańsk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolishBase Context triple: [Bitwa pod Oliwą, hasPolishBase, Gdańsk]
-
A.
isPolish
Indicates that an entity has the property of being Polish, typically in terms of nationality, origin, or cultural affiliation.
-
B.
hasNameInPolish
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
C.
hasSilesianName
Indicates that an entity is associated with a name expressed in the Silesian language.
-
D.
hasPolishFlagship
Indicates that an entity serves as the primary or most important representative (flagship) of something specifically within the context of Poland or the Polish domain.
-
E.
hasPolishShip
Indicates that an entity possesses or is associated with a ship that is Polish.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffe23081408190a121d901dbce1403 |
completed | May 10, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ffe18aed348190912a5996b2da728b |
completed | May 10, 2026, 1:38 a.m. |
| PDg | Predicate description generation | batch_69ffe22f453c81909867ee2d2047636f |
completed | May 10, 2026, 1:41 a.m. |
Created at: May 3, 2026, 4:19 p.m.