Triple
T28997138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapporo Concert Hall Kitara |
E736196
|
entity |
| Predicate | pipeOrganType |
P165883
|
FINISHED |
| Object | concert hall pipe organ |
—
|
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: concert hall pipe organ | Statement: [Sapporo Concert Hall Kitara, pipeOrganType, concert hall pipe organ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pipeOrganType Context triple: [Sapporo Concert Hall Kitara, pipeOrganType, concert hall pipe organ]
-
A.
pipeType
Indicates the specific kind or category of pipe associated with or used in relation to an entity.
-
B.
pipeDiameter
Indicates that one entity specifies or measures the diameter of a pipe associated with another entity.
-
C.
penstockType
Indicates the specific kind or classification of a penstock used in a water conveyance or hydroelectric system.
-
D.
inletType
Indicates the specific kind or category of inlet through which something (such as a fluid, signal, or material) enters a system or component.
-
E.
hasPipes
Indicates that one entity is equipped with, contains, or is connected to one or more pipes.
- F. None of above. chosen
Provenance (4 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fb6ef4881909a758c3538fdec03 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:32 a.m.