Triple
T16395905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biała |
E398177
|
entity |
| Predicate | mergedEntityType |
P123259
|
FINISHED |
| Object | city |
—
|
LITERAL FINISHED |
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: city | Statement: [Biała, mergedEntityType, city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedEntityType Context triple: [Biała, mergedEntityType, city]
-
A.
includedEntityType
Indicates that one entity type is contained within, or forms a component part of, another entity type.
-
B.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
C.
isMergedEntityOf
Indicates that one entity is the result of combining or consolidating two or more other entities into a single merged entity.
-
D.
mergedInto
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
E.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326462298819087091dc935f0f916 |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.