Triple
T739973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corfield v. Coryell |
E15220
|
entity |
| Predicate | hasApproximateDecisionDate |
P877
|
FINISHED |
| Object | May 1823 |
—
|
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: May 1823 | Statement: [Corfield v. Coryell, hasApproximateDecisionDate, May 1823]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDecisionDate Context triple: [Corfield v. Coryell, hasApproximateDecisionDate, May 1823]
-
A.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
-
B.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
C.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
E.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fc734c81908fbd36386d5746d6 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.