Triple
T7880040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ncome Museum |
E182953
|
entity |
| Predicate | interpretsEventDate |
P830
|
FINISHED |
| Object | 16 December 1838 |
—
|
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: 16 December 1838 | Statement: [Ncome Museum, interpretsEventDate, 16 December 1838]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretsEventDate Context triple: [Ncome Museum, interpretsEventDate, 16 December 1838]
-
A.
interpretsEvent
Indicates that an entity analyzes and assigns meaning or significance to an event.
-
B.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
C.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
D.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
E.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39be7ab88190affcd353a0cd37fa |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:58 p.m.