Triple
T24890846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szczawin Kościelny |
E622994
|
entity |
| Predicate | hasAdministrativeTieTo |
P37165
|
FINISHED |
| Object | Gostynin |
—
|
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: Gostynin | Statement: [Szczawin Kościelny, hasAdministrativeTieTo, Gostynin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeTieTo Context triple: [Szczawin Kościelny, hasAdministrativeTieTo, Gostynin]
-
A.
hasAdministrativeEquivalent
Indicates that two entities hold equivalent roles, powers, or status within an administrative or governance structure.
-
B.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
C.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
associatedWithAdministration
chosen
Indicates a relationship in which an entity is connected to, involved in, or under the responsibility of an administrative body, process, or function.
-
E.
hasCapitalAdministered
Indicates that a specified capital city is responsible for administering or governing a particular territory or political entity.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:26 a.m.