Triple
T10425162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Journal |
E245765
|
entity |
| Predicate | isArchivedBy |
P39745
|
FINISHED |
| Object | legislative 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: legislative archives | Statement: [House Journal, isArchivedBy, legislative archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isArchivedBy Context triple: [House Journal, isArchivedBy, legislative archives]
-
A.
archivesStatus
Indicates the current archival state or condition assigned to an item, such as whether it is archived, active, or pending archiving.
-
B.
isWithheldBy
Indicates that something (such as information, resources, or permission) is deliberately not given, released, or made available by a particular entity.
-
C.
archivesHeldBy
chosen
Indicates that archival materials or records are kept, managed, or preserved by a particular entity.
-
D.
isPostedBy
Indicates that a piece of content (such as a message, post, or item) was created and published by a particular user or source.
-
E.
hasNotableArchive
Indicates that an entity maintains or is associated with an archive that is considered significant or noteworthy.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea48cb348190ad4432f263300592 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:12 p.m.