Triple
T27849844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Clock at Alexanderplatz |
E703919
|
entity |
| Predicate | continentShown |
P121983
|
FINISHED |
| Object | Europe |
—
|
NE NERFINISHED |
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: Europe | Statement: [World Clock at Alexanderplatz, continentShown, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentShown Context triple: [World Clock at Alexanderplatz, continentShown, Europe]
-
A.
continentFound
Indicates that a specified continent is the location where a particular entity is found or occurs.
-
B.
continentReference
chosen
Indicates that one entity serves as a reference or pointer to a specific continent associated with another entity.
-
C.
continentScope
Indicates that something applies within, is limited to, or is defined at the level of a specific continent.
-
D.
continentIncludes
Indicates that a particular continent geographically contains or encompasses a specified region, country, or area.
-
E.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 6:10 p.m.