Triple
T612718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gdynia |
E12134
|
entity |
| Predicate | rapidDevelopmentPeriod |
P16148
|
FINISHED |
| Object | interwar period |
—
|
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: interwar period | Statement: [Gdynia, rapidDevelopmentPeriod, interwar period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rapidDevelopmentPeriod Context triple: [Gdynia, rapidDevelopmentPeriod, interwar period]
-
A.
developedRapidlyDuring
chosen
Indicates that one entity experienced swift or accelerated development within the time period or context defined by another entity.
-
B.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
D.
developedAt
Indicates the place or location where something was created, built, or developed.
-
E.
standardReleaseCadence
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e08dbf88190ab050078a63e266b |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfa7b4481909bec7a5fd3e98c65 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.