Triple
T22192295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midmer-Losh pipe organ |
E548458
|
entity |
| Predicate | hasConsoleType |
P96660
|
FINISHED |
| Object | main console |
—
|
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: main console | Statement: [Midmer-Losh pipe organ, hasConsoleType, main console]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsoleType Context triple: [Midmer-Losh pipe organ, hasConsoleType, main console]
-
A.
hasScreenType
Indicates the specific kind or category of screen associated with or used by an entity.
-
B.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
C.
has terminal type
chosen
Indicates that an entity is associated with a specific terminal type or category it belongs to.
-
D.
hasIntegratedTerminal
Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
-
E.
hasSoftwareType
Indicates that an entity is associated with or classified under a particular type or category of software.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae49ec881908fa42446b19e3f2d |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.