Triple
T26359567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa pod Kockiem |
E660161
|
entity |
| Predicate | belongsToTheatre |
P179999
|
FINISHED |
| Object | działania lądowe w Polsce 1939 |
—
|
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: działania lądowe w Polsce 1939 | Statement: [Bitwa pod Kockiem, belongsToTheatre, działania lądowe w Polsce 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToTheatre Context triple: [Bitwa pod Kockiem, belongsToTheatre, działania lądowe w Polsce 1939]
-
A.
belongsToCinema
Indicates that something is part of, associated with, or under the ownership/management of a particular cinema.
-
B.
isPartOfTheater
Indicates that one entity functions as a component, section, or subdivision within a larger theater (such as a theater building, complex, or organizational unit).
-
C.
ownsTheatre
Indicates that one entity has legal ownership or controlling possession of a theatre.
-
D.
intendedTheatre
Indicates a relationship where an entity is planned, designed, or meant to be performed, shown, or take place in a particular theatre.
-
E.
hasNeighbouringTheatre
Indicates that one theatre is located close enough to another theatre to be considered its neighbor.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 26, 2026, 10:50 p.m.