Triple
T267628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcussen & Søn pipe organ |
E5765
|
entity |
| Predicate | tunedTo |
P4577
|
FINISHED |
| Object | equal temperament (typical for concert use) |
—
|
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: equal temperament (typical for concert use) | Statement: [Marcussen & Søn pipe organ, tunedTo, equal temperament (typical for concert use)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunedTo Context triple: [Marcussen & Søn pipe organ, tunedTo, equal temperament (typical for concert use)]
-
A.
adaptedTo
chosen
Indicates that one entity has been modified, adjusted, or evolved to function effectively within the conditions, requirements, or characteristics defined by another entity.
-
B.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
C.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
D.
soundCarrier
Indicates that one entity serves as a medium or object that carries, stores, or transmits sound for another entity.
-
E.
playedAfter
Indicates that one event, performance, or action occurred later in time than another.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dacf60c8190a5c3ef455b9a8b20 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.