Triple
T10948905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bitwa pod Kutnem |
E258672
|
entity |
| Predicate | data |
P96786
|
FINISHED |
| Object | wrzesień 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: wrzesień 1939 | Statement: [bitwa pod Kutnem, data, wrzesień 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: data Context triple: [bitwa pod Kutnem, data, wrzesień 1939]
-
A.
dataFile
Indicates a relationship where one entity serves as or is associated with a specific data file used, stored, or referenced by another entity.
-
B.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
C.
dataContext
Indicates the situational or environmental conditions under which data is produced, interpreted, or used, such as source, scope, assumptions, and relevant constraints.
-
D.
dataAcquisition
Indicates the process by which one entity obtains, collects, or retrieves data from another source or system.
-
E.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ec7028819084f5ce2035a128e4 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.