Triple
T10699820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rensselaer Russell Nelson |
E252242
|
entity |
| Predicate | commissionReceivedDate |
P68092
|
FINISHED |
| Object | 1858-05-11 |
—
|
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: 1858-05-11 | Statement: [Rensselaer Russell Nelson, commissionReceivedDate, 1858-05-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionReceivedDate Context triple: [Rensselaer Russell Nelson, commissionReceivedDate, 1858-05-11]
-
A.
dateReceived
chosen
Indicates the point in time when something (such as a message, item, or document) was received by a recipient.
-
B.
revenueDate
Indicates the date on which revenue is recognized, recorded, or attributed in relation to a transaction or financial event.
-
C.
acknowledgmentDate
Indicates the date on which an acknowledgment of something (such as receipt, notice, or information) is formally recorded or recognized.
-
D.
sentenceConfirmationDate
Indicates the date on which a sentence (e.g., legal judgment or decision) is formally confirmed or finalized.
-
E.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd8abd7c81909c274aa1699a3695 |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.