Triple
T30107924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ε 201 |
E765181
|
entity |
| Predicate | hasCatalogNumberSystem |
P195085
|
FINISHED |
| Object | von Soden |
—
|
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: von Soden | Statement: [ε 201, hasCatalogNumberSystem, von Soden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogNumberSystem Context triple: [ε 201, hasCatalogNumberSystem, von Soden]
-
A.
hasCatalogNumberPrefix
Indicates that an item’s catalog number begins with a specified prefix.
-
B.
hasCabinetNumberingSystem
Indicates that there is a specific scheme or method used to assign and organize identification numbers to cabinets.
-
C.
usesHarmonizedNumberingWith
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
-
D.
hasTrackNumberingScheme
Indicates that an entity uses or is associated with a specific scheme or system for numbering tracks.
-
E.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
- F. None of above. chosen
Provenance (4 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: April 29, 2026, 7:09 p.m.