Triple
T25978273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Błędne Skały |
E645999
|
entity |
| Predicate | hasPolishNameMeaning |
P15778
|
FINISHED |
| Object | Errant Rocks |
—
|
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: Errant Rocks | Statement: [Błędne Skały, hasPolishNameMeaning, Errant Rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolishNameMeaning Context triple: [Błędne Skały, hasPolishNameMeaning, Errant Rocks]
-
A.
hasNameInPolish
chosen
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
B.
hasKashubianName
Indicates that an entity is associated with a specific name in the Kashubian language.
-
C.
hasLatinNameMeaning
Indicates that an entity’s Latin name conveys a specific meaning or refers to a particular concept.
-
D.
hasSilesianName
Indicates that an entity is associated with a name expressed in the Silesian language.
-
E.
isPolish
Indicates that an entity has the property of being Polish, typically in terms of nationality, origin, or cultural affiliation.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 22, 2026, 8:52 a.m.