Triple
T28900195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIN 41612 |
E732931
|
entity |
| Predicate | hasContactDesignation |
P201561
|
FINISHED |
| Object | rows A, B, C |
—
|
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: rows A, B, C | Statement: [DIN 41612, hasContactDesignation, rows A, B, C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactDesignation Context triple: [DIN 41612, hasContactDesignation, rows A, B, C]
-
A.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
hasDesignationFor
Indicates that one entity assigns or holds a specific title, label, or formal designation for another entity.
-
C.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
D.
hasDesignationStatus
Indicates that an entity holds a particular official designation or status within a defined classification or recognition system.
-
E.
hasIspDesignation
Indicates that an entity has been assigned a specific Internet Service Provider (ISP) designation or classification.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
| PDg | Predicate description generation | batch_6a00053cdcb08190980df73e235e9ad8 |
completed | May 10, 2026, 4:10 a.m. |
Created at: April 28, 2026, 8:02 a.m.