Triple
T16515775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSA |
E401178
|
entity |
| Predicate | archiveLevel |
P66614
|
FINISHED |
| Object | state-level archives |
—
|
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: state-level archives | Statement: [NYSA, archiveLevel, state-level archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archiveLevel Context triple: [NYSA, archiveLevel, state-level archives]
-
A.
archivesLevel
chosen
Indicates that one entity is stored, classified, or maintained at a particular archival level or tier within an archival system.
-
B.
archiveOf
Indicates that one entity serves as a stored collection or repository preserving the records, documents, or materials of another entity.
-
C.
archiveFor
Indicates that one entity serves as a storage or preservation repository specifically for the records, documents, or data of another entity.
-
D.
archiveType
Indicates the classification or category assigned to an archive within a system or collection.
-
E.
archivesRole
Indicates that one entity serves as the archival custodian or role responsible for preserving, maintaining, or storing another 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7bbfa481909037148cdb4d8996 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.