Triple
T33770031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boy Willie |
E865352
|
entity |
| Predicate | hasFamilyHeirloom |
P20494
|
FINISHED |
| Object | Charles family 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: Charles family piano | Statement: [Boy Willie, hasFamilyHeirloom, Charles family piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyHeirloom Context triple: [Boy Willie, hasFamilyHeirloom, Charles family piano]
-
A.
hasHeirloom
chosen
Indicates that one entity possesses or is associated with an heirloom originating from another entity.
-
B.
hasHereditaryLegacy
Indicates that an entity possesses a legacy, status, or attribute that is passed down through familial or ancestral inheritance.
-
C.
hasJewel
Indicates that one entity possesses, contains, or is adorned with a jewel in relation to another entity.
-
D.
hasFamilyTrait
Indicates that a particular trait or characteristic is shared among members of the same family or lineage.
-
E.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:45 a.m.