Triple
T29180406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flower Piece |
E739729
|
entity |
| Predicate | commonlyRecordedBy |
P46689
|
FINISHED |
| Object | concert pianists |
—
|
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: concert pianists | Statement: [Flower Piece, commonlyRecordedBy, concert pianists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyRecordedBy Context triple: [Flower Piece, commonlyRecordedBy, concert pianists]
-
A.
frequentlyRecordedBy
chosen
Indicates that an entity is often documented, captured, or logged by a particular agent, system, or recording process.
-
B.
isOftenRecordedOn
Indicates that something is frequently documented, captured, or stored using a particular medium, format, or recording method.
-
C.
isOftenRecordedWith
Indicates that one entity is frequently documented, captured, or logged at the same time as another entity.
-
D.
areRecordedBy
Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
-
E.
mainlyRecordedBy
Indicates that the primary or most significant recording of something (such as a work, event, or data set) was made by a particular agent or entity.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 11:57 a.m.