Triple
T5803888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Archives |
E128692
|
entity |
| Predicate | archivesLevel |
P66614
|
FINISHED |
| Object | state level |
—
|
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 | Statement: [Maine State Archives, archivesLevel, state level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivesLevel Context triple: [Maine State Archives, archivesLevel, state level]
-
A.
archivesStatus
Indicates the current archival state or condition assigned to an item, such as whether it is archived, active, or pending archiving.
-
B.
archivesScope
Indicates that one entity defines or delimits the scope or coverage of another entity’s archival content or records.
-
C.
archivesType
Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
-
D.
archivesRole
Indicates that one entity serves as the archival custodian or role responsible for preserving, maintaining, or storing another entity.
-
E.
archivesModel
Indicates that one entity stores and preserves another entity as an archived model for long-term reference or retrieval.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b10def8819080859bc6505405ed |
completed | March 22, 2026, 5:46 p.m. |
Created at: March 22, 2026, 3:52 p.m.