Triple
T16110293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammarby Sjöstad |
E390853
|
entity |
| Predicate | majorDevelopmentPhase |
P22203
|
FINISHED |
| Object | 2000s |
—
|
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: 2000s | Statement: [Hammarby Sjöstad, majorDevelopmentPhase, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorDevelopmentPhase Context triple: [Hammarby Sjöstad, majorDevelopmentPhase, 2000s]
-
A.
mainDevelopmentPeriod
chosen
Indicates the primary time span during which the main development or formation of something took place.
-
B.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
C.
developmentPhaseName
Indicates the specific stage or phase name within a broader development process or lifecycle.
-
D.
underDevelopment
Indicates that something is currently being created, improved, or worked on and is not yet in its final or completed state.
-
E.
significantDevelopmentUnder
Indicates that one entity has undergone a major or notable development, change, or advancement under the influence, authority, or conditions provided by another entity.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016665c0819081aa7a44b1d08183 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.