Triple
T17400318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Green Clemson |
E423067
|
entity |
| Predicate | willSignedDate |
P439
|
FINISHED |
| Object | 1886-11-06 |
—
|
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: 1886-11-06 | Statement: [Thomas Green Clemson, willSignedDate, 1886-11-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willSignedDate Context triple: [Thomas Green Clemson, willSignedDate, 1886-11-06]
-
A.
willSignedOn
Indicates that a person has formally signed a will on a specific date or occasion, thereby validating or executing that testamentary document.
-
B.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
C.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
D.
signaturesTargetDate
Indicates the date by which the required signatures are expected to be obtained or completed.
-
E.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43ac0596481908c400916d5c1b971 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.