Triple
T12685896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Corelli's Mandolin |
E303063
|
entity |
| Predicate | hasInstrumentInTitle |
P103300
|
FINISHED |
| Object | mandolin |
—
|
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: mandolin | Statement: [Captain Corelli's Mandolin, hasInstrumentInTitle, mandolin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstrumentInTitle Context triple: [Captain Corelli's Mandolin, hasInstrumentInTitle, mandolin]
-
A.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
B.
hasInstrumentNamedAfter
Indicates that an entity has an instrument that is named in honor of, or derived from the name of, another entity.
-
C.
hasNotableInstrumentNamedAfter
Indicates that an entity has a notable musical instrument that is named after it.
-
D.
hasTitleFeature
chosen
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
-
E.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961d7cd4c81909521839ef5859799 |
completed | April 10, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.