Triple
T5426310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sentrum borough |
E121369
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Youngstorget |
E142868
|
NE 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: Youngstorget | Statement: [Sentrum borough, contains, Youngstorget]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Youngstorget Context triple: [Sentrum borough, contains, Youngstorget]
-
A.
Youngstorget
chosen
Youngstorget is a central public square in Oslo, Norway, known as a historic hub for political rallies, labor movement events, and urban social life.
-
B.
Hötorget
Hötorget is a central square in downtown Stockholm known for its market stalls, surrounding shops, and cultural venues.
-
C.
Gustav Adolfs torg
Gustav Adolfs torg is a central public square in Stockholm, Sweden, known for its historic buildings, cultural institutions, and role as a prominent civic and ceremonial space.
-
D.
Stortorvet
Stortorvet is a central public square in downtown Oslo, Norway, known as a busy transport hub and commercial meeting place.
-
E.
Fridhemsplan
Fridhemsplan is a major public square and transport hub in central Stockholm, known for its busy metro interchange and surrounding commercial area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd881598448190a9bb456dee36004b |
completed | March 20, 2026, 5:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf4125e490819088f70090cf8d81fa |
completed | March 22, 2026, 1:08 a.m. |
Created at: March 20, 2026, 2:06 p.m.