Triple
T26073010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dia!kwain |
E657600
|
entity |
| Predicate | roleInArchive |
P52797
|
FINISHED |
| Object | key informant |
—
|
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: key informant | Statement: [Dia!kwain, roleInArchive, key informant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInArchive Context triple: [Dia!kwain, roleInArchive, key informant]
-
A.
archivesRole
chosen
Indicates that one entity serves as the archival custodian or role responsible for preserving, maintaining, or storing another entity.
-
B.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
C.
roleInLibrary
Indicates the specific function, position, or responsibility an entity holds within a library context.
-
D.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
-
E.
heritageOrganizationRole
Indicates the specific role or function an entity holds within a heritage-related organization.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 26, 2026, 7:31 p.m.