Triple
T35900792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HALS |
E1038345
|
entity |
| Predicate | recordsStoredAt |
P195792
|
FINISHED |
| Object | Library of Congress |
—
|
NE NERFINISHED |
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: Library of Congress | Statement: [HALS, recordsStoredAt, Library of Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsStoredAt Context triple: [HALS, recordsStoredAt, Library of Congress]
-
A.
samplesStoredAt
Indicates that physical or digital samples are kept or maintained at a specific location or facility.
-
B.
recordsWith
Indicates that one entity keeps or maintains documented information about another entity or event.
-
C.
recordsOn
Indicates that one entity documents, stores, or logs information about another entity on a particular medium, system, or date.
-
D.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
E.
recordSetAt
Indicates that a record or data entry was created, stored, or established at a specific time or location.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69fde5d677b88190bc904e6df8617c18 |
completed | May 8, 2026, 1:32 p.m. |
Created at: May 3, 2026, 4:07 p.m.