Triple
T16715264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Killer |
E406207
|
entity |
| Predicate | bearerInstrument |
P11385
|
FINISHED |
| Object | piano |
—
|
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: piano | Statement: [The Killer, bearerInstrument, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerInstrument Context triple: [The Killer, bearerInstrument, piano]
-
A.
bearerField
Indicates that one entity serves as the bearer or holder of a specific field, attribute, or property associated with another entity.
-
B.
bearerInstanceOf
Indicates that a bearer (such as an agent, object, or entity) is an instance or specific realization of a more general class, type, or role.
-
C.
bearerType
Indicates the type or category of entity that serves as the bearer or holder in a given relationship or context.
-
D.
bearer
chosen
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
E.
bearerAlignedWith
Indicates that the bearer’s position, orientation, or stance is arranged in line with, or matches, that of another specified reference.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38654ee4c8190abf36c29d6610a96 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.