Triple
T26287946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krieblowitz estate |
E661188
|
entity |
| Predicate | currentLocalName |
P113224
|
FINISHED |
| Object | Krobielowice estate |
—
|
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: Krobielowice estate | Statement: [Krieblowitz estate, currentLocalName, Krobielowice estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLocalName Context triple: [Krieblowitz estate, currentLocalName, Krobielowice estate]
-
A.
hasLocalName
Indicates that an entity is known by a specific name or designation within a particular local language, script, or regional context.
-
B.
hasLocalNameFor
Indicates that one entity serves as the local or context-specific name or label used to refer to another entity.
-
C.
currentName
Indicates the present or most recently assigned name associated with an entity.
-
D.
modernLocalName
chosen
Indicates the current, locally used name or designation for an entity, as recognized in the present time.
-
E.
localNameDefinition
Indicates that an entity’s locally scoped name is defined or specified within a particular context or namespace.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 26, 2026, 10:06 p.m.