Triple
T29326002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English horn |
E743643
|
entity |
| Predicate | isLowerInPitchThan |
P111287
|
FINISHED |
| Object | oboe |
—
|
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: oboe | Statement: [English horn, isLowerInPitchThan, oboe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowerInPitchThan Context triple: [English horn, isLowerInPitchThan, oboe]
-
A.
hasLowerFrequencyIn
Indicates that one entity occurs or appears less frequently within a specified context than another entity.
-
B.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
C.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
D.
relativePitch
chosen
Indicates a relationship where one entity’s pitch is defined or compared in terms of its interval or distance from another entity’s pitch.
-
E.
hasLowForm
Indicates that an entity possesses a lower or less developed form, version, or level of something relative to a standard or comparison.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66895a0d481908efba5930e1ec3b9 |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:26 p.m.