Triple
T37799587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa pod Oliwą |
E942332
|
entity |
| Predicate | hasSwedishFlagship |
P189539
|
FINISHED |
| Object | „Tigern” |
—
|
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: „Tigern” | Statement: [Bitwa pod Oliwą, hasSwedishFlagship, „Tigern”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSwedishFlagship Context triple: [Bitwa pod Oliwą, hasSwedishFlagship, „Tigern”]
-
A.
hasFlagshipInstitution
Indicates that one entity serves as the primary or leading institution associated with another entity, such as an organization, system, or network.
-
B.
hasFlagshipIn
Indicates that an entity designates a particular location or branch as its primary or flagship presence.
-
C.
hasFlagshipCampusOf
Indicates that one location serves as the primary or main campus for a particular institution or organization.
-
D.
firstFlagship
Indicates that an entity is the earliest or original flagship among a set of flagships associated with another entity.
-
E.
hasFlagshipSpecies
Indicates that one entity (typically a site, region, or conservation program) is associated with or represented by a particular flagship species used to promote awareness or protection.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.