Triple
T28206069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Fletcher |
E717024
|
entity |
| Predicate | fictionalInstrument |
P84710
|
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: [Alex Fletcher, fictionalInstrument, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalInstrument Context triple: [Alex Fletcher, fictionalInstrument, piano]
-
A.
fictionalInvention
Indicates that one entity is an invention or creation that exists only within the fictional context of another entity (such as a story, universe, or work).
-
B.
fictionalObject
chosen
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
C.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular instrument.
-
D.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
E.
inspiredInstrument
Indicates that one entity served as the creative inspiration or model for the design, creation, or development of another instrument.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 10:35 p.m.