Triple
T36271449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OM (Orchestra Model) guitar |
E892683
|
entity |
| Predicate | hasMoreNoteSeparationThan |
P199690
|
FINISHED |
| Object | dreadnought guitar |
—
|
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: dreadnought guitar | Statement: [OM (Orchestra Model) guitar, hasMoreNoteSeparationThan, dreadnought guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoreNoteSeparationThan Context triple: [OM (Orchestra Model) guitar, hasMoreNoteSeparationThan, dreadnought guitar]
-
A.
hasNumberOfNotes
Indicates the relationship that specifies how many notes are associated with a given entity.
-
B.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
-
C.
knownSeparation
Indicates that a separation or split between entities is recognized or has been established as a known fact.
-
D.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
-
E.
separatedUntil
Indicates that two entities remain apart or not in contact up to a specified time or condition.
- F. None of above. chosen
Provenance (4 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
| PDg | Predicate description generation | batch_69ff4fc5289c819084abd5ede185e96b |
completed | May 9, 2026, 3:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.