Triple
T23988902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemeinsame Normdatei |
E605009
|
entity |
| Predicate | hasCatalogingRules |
P2846
|
FINISHED |
| Object | Resource Description and Access |
—
|
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: Resource Description and Access | Statement: [Gemeinsame Normdatei, hasCatalogingRules, Resource Description and Access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogingRules Context triple: [Gemeinsame Normdatei, hasCatalogingRules, Resource Description and Access]
-
A.
belongsToCatalogOf
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
B.
hasCatalogView
Indicates that an entity is associated with a particular way or mode of viewing or presenting a catalog.
-
C.
hasRuleCharacteristic
Indicates that something possesses a specific property, feature, or attribute related to a rule or set of rules.
-
D.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
E.
hasNumberOfRules
Indicates the specific count of rules associated with or applicable to an 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38902fc8190af51cedfce1c6c13 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:37 p.m.