Triple
T4794406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick Corbin |
E106676
|
entity |
| Predicate | contractSigningDate |
P439
|
FINISHED |
| Object | 2018-12 |
—
|
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: 2018-12 | Statement: [Patrick Corbin, contractSigningDate, 2018-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractSigningDate Context triple: [Patrick Corbin, contractSigningDate, 2018-12]
-
A.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
issuedDocumentDate
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
-
C.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
-
D.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
E.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd66088d588190839acfbac6e1c3dd |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.