Triple
T1093354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shriver House Museum |
E24215
|
entity |
| Predicate | eraInterpreted |
P23789
|
FINISHED |
| Object | 1860s |
—
|
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: 1860s | Statement: [Shriver House Museum, eraInterpreted, 1860s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraInterpreted Context triple: [Shriver House Museum, eraInterpreted, 1860s]
-
A.
isInterpretedBy
Indicates that something (such as data, a work, or a signal) is given meaning, understanding, or explanation by a particular agent or process.
-
B.
isInterpretedDifferentlyIn
Indicates that the same item, event, or expression is understood or construed in a different way within a specified context, group, or setting.
-
C.
interpretiveStatus
Indicates the evaluative or explanatory stance assigned to something, such as how it is understood, classified, or interpreted within a given context.
-
D.
eraCode
Indicates the specific historical or temporal era associated with an entity, typically encoded as a standardized era identifier.
-
E.
interpretedInCase
Indicates that something is understood, analyzed, or given meaning within the context of a particular case or specific situational scenario.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99bd06c8190bce1d77b0337b07c |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b743175481908f3967e589717c55 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.