Triple
T4327614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Register Office for England and Wales |
E96669
|
entity |
| Predicate | recordsStartDate |
P45301
|
FINISHED |
| Object | 1837 |
—
|
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: 1837 | Statement: [General Register Office for England and Wales, recordsStartDate, 1837]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsStartDate Context triple: [General Register Office for England and Wales, recordsStartDate, 1837]
-
A.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
B.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
-
C.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
-
D.
inscriptionDate
Indicates the date on which an inscription was created, carved, or formally recorded.
-
E.
startDateOfCollection
chosen
Indicates the calendar date on which a particular collection or collecting activity begins.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35131f11881909e2d5415a70d5785 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.