Triple
T34490791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cello Concerto No. 1 |
E885459
|
entity |
| Predicate | hasLaterCompanionWork |
P31222
|
FINISHED |
| Object | Cello Concerto No. 2 |
—
|
NE NERFINISHED |
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: Cello Concerto No. 2 | Statement: [Cello Concerto No. 1, hasLaterCompanionWork, Cello Concerto No. 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterCompanionWork Context triple: [Cello Concerto No. 1, hasLaterCompanionWork, Cello Concerto No. 2]
-
A.
hasPrecedingWork
Indicates that one work comes before another in a sequence, serving as its predecessor.
-
B.
hasSubsequentWork
chosen
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
-
C.
hasCompanionCase
Indicates that an entity is associated with another related case that accompanies or parallels it.
-
D.
laterWorksAs
Indicates that an entity holds or takes on a particular occupation or role at a later point in time relative to another referenced time or role.
-
E.
laterWorkBy
Indicates that one work was created after another work by the same creator or author.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 1, 2026, 2:01 a.m.