Triple
T9042528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nightwatchman |
E216667
|
entity |
| Predicate | activeInstrument |
P12878
|
FINISHED |
| Object | acoustic 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: acoustic guitar | Statement: [The Nightwatchman, activeInstrument, acoustic guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInstrument Context triple: [The Nightwatchman, activeInstrument, acoustic guitar]
-
A.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
B.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
hostInstrument
Indicates that one entity serves as the instrument or platform that hosts, carries, or enables another entity or process.
-
E.
musicInstrumentation
chosen
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b1228748190be0c4afe6e0bd9a3 |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.