Triple
T9198247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISNI database |
E220768
|
entity |
| Predicate | primaryKey |
P60234
|
FINISHED |
| Object | ISNI identifier |
—
|
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: ISNI identifier | Statement: [ISNI database, primaryKey, ISNI identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryKey Context triple: [ISNI database, primaryKey, ISNI identifier]
-
A.
primaryIndex
Indicates that one entity serves as the main or default index used to organize, access, or reference another entity within a system or dataset.
-
B.
usesPrimaryKey
chosen
Indicates that one entity relies on or references another entity’s primary key as its main means of identification or linkage.
-
C.
primaryField
Indicates the main area of focus, discipline, or domain most centrally associated with an entity.
-
D.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
E.
primaryIdentification
Indicates that one identifier is the main or officially recognized identification for an entity among possibly multiple identifiers.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd880ab808190aa785a5f1e5d5976 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.