Triple
T28997139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapporo Concert Hall Kitara |
E736196
|
entity |
| Predicate | pipeOrganManuals |
P17558
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Sapporo Concert Hall Kitara, pipeOrganManuals, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pipeOrganManuals Context triple: [Sapporo Concert Hall Kitara, pipeOrganManuals, 4]
-
A.
organManuals
chosen
Indicates a relationship where specific manuals or keyboards belong to, are part of, or are associated with a particular organ instrument.
-
B.
pipeOrganType
Indicates that one entity is a specific type or classification of pipe organ relative to another entity.
-
C.
diagnosticManual
Indicates that one entity serves as the diagnostic manual or classification system used to define, categorize, or code the other entity’s condition or diagnosis.
-
D.
pipeType
Indicates the specific kind or category of pipe associated with or used in relation to an entity.
-
E.
органЭмиссии
Indicates the authority or body responsible for issuing or emitting something (such as a document, instrument, or asset).
- 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_69f65fb6ef4881909a758c3538fdec03 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:32 a.m.