Triple
T28997141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapporo Concert Hall Kitara |
E736196
|
entity |
| Predicate | pipeOrganPipesApprox |
P3426
|
FINISHED |
| Object | 4700 |
—
|
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: 4700 | Statement: [Sapporo Concert Hall Kitara, pipeOrganPipesApprox, 4700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pipeOrganPipesApprox Context triple: [Sapporo Concert Hall Kitara, pipeOrganPipesApprox, 4700]
-
A.
pipeOrganType
Indicates that one entity is a specific type or classification of pipe organ relative to another entity.
-
B.
numberOfOrganPipes
chosen
Indicates the quantitative relationship specifying how many organ pipes are associated with a given organ or organ-related entity.
-
C.
pipeType
Indicates the specific kind or category of pipe associated with or used in relation to an entity.
-
D.
hasPipes
Indicates that one entity is equipped with, contains, or is connected to one or more pipes.
-
E.
pipeDiameter
Indicates that one entity specifies or measures the diameter of a pipe associated with 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 9:32 a.m.