Triple
T31210307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walther Kranz |
E795718
|
entity |
| Predicate | hasDielsKranzNumbering |
P37553
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Walther Kranz, hasDielsKranzNumbering, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDielsKranzNumbering Context triple: [Walther Kranz, hasDielsKranzNumbering, yes]
-
A.
hasKochelNumber
Indicates that a musical work is associated with a specific Köchel catalogue number used to uniquely identify compositions by Mozart.
-
B.
hasDesignationNumber
Indicates that an entity is associated with a specific official designation or identification number.
-
C.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
D.
usesHarmonizedNumberingWith
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
-
E.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 29, 2026, 9:09 p.m.