Triple
T8593230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paavo Nurmi statue in Helsinki |
E203479
|
entity |
| Predicate | typicalView |
P61564
|
FINISHED |
| Object | Paavo Nurmi in running pose |
—
|
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: Paavo Nurmi in running pose | Statement: [Paavo Nurmi statue in Helsinki, typicalView, Paavo Nurmi in running pose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalView Context triple: [Paavo Nurmi statue in Helsinki, typicalView, Paavo Nurmi in running pose]
-
A.
traditionalView
Indicates that one entity holds or represents a conventional, long-established perspective or interpretation about another entity or topic.
-
B.
viewType
Indicates the specific manner or format in which something is displayed, presented, or visually arranged.
-
C.
typicalVisualStyle
chosen
Indicates the characteristic or commonly observed visual appearance or aesthetic style associated with an entity.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.