Triple
T29179752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schumann Symphony No. 4 |
E739712
|
entity |
| Predicate | placeOfRevision |
P154136
|
FINISHED |
| Object | Düsseldorf |
—
|
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: Düsseldorf | Statement: [Schumann Symphony No. 4, placeOfRevision, Düsseldorf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfRevision Context triple: [Schumann Symphony No. 4, placeOfRevision, Düsseldorf]
-
A.
revisionPlace
chosen
Indicates the location where a revision or modification of something took place.
-
B.
revisionOf
Indicates that one entity is a modified or updated version of another earlier entity.
-
C.
coreRevision
Indicates that one entity is a fundamental or primary revision of another, representing a central update or modification in a versioning or editing process.
-
D.
revisionMechanism
Indicates the method or process by which something is updated, corrected, or modified over time.
-
E.
revisedVersionType
Indicates that one entity is a revised form of another, specifying the type or nature of the revision made.
- 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 11:56 a.m.