Triple
T9167709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Wesley Longyear |
E220002
|
entity |
| Predicate | commissionReceivedOn |
P6782
|
FINISHED |
| Object | 1870-02-18 |
—
|
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: 1870-02-18 | Statement: [John Wesley Longyear, commissionReceivedOn, 1870-02-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionReceivedOn Context triple: [John Wesley Longyear, commissionReceivedOn, 1870-02-18]
-
A.
commissionedAfter
Indicates that one entity was formally authorized, ordered, or initiated at a later time than another entity.
-
B.
commissionedAt
chosen
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
-
C.
dateReceived
Indicates the point in time when something (such as a message, item, or document) was received by a recipient.
-
D.
commissionOutcome
Indicates the result or consequence produced by a commission, such as whether it was successful, failed, or led to a particular decision or action.
-
E.
revenueDate
Indicates the date on which revenue is recognized, recorded, or attributed in relation to a transaction or financial event.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaadfb50881909b9127f92e4b3e21 |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.