Triple
T30072572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler 10 |
E764224
|
entity |
| Predicate | autographLocation |
P18545
|
FINISHED |
| Object | Österreichische Nationalbibliothek |
—
|
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: Österreichische Nationalbibliothek | Statement: [Mahler 10, autographLocation, Österreichische Nationalbibliothek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autographLocation Context triple: [Mahler 10, autographLocation, Österreichische Nationalbibliothek]
-
A.
signatureLocation
chosen
Indicates the place or position where a signature is written, recorded, or otherwise applied.
-
B.
signedArtist
Indicates that an artist has entered into a formal contract or agreement with a label, company, or representative.
-
C.
marksLocationOf
Indicates that one entity serves as a marker, sign, or indicator specifying the location of another entity.
-
D.
apogeeLocation
Indicates the location in space where an orbiting object is at its farthest point (apogee) from the body it orbits.
-
E.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d3a1a048190a40fef6e237dcf90 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:01 p.m.