Triple
T622966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi University for Women v. Hogan |
E14552
|
entity |
| Predicate | decidedDate |
P2232
|
FINISHED |
| Object | 1982-07-01 |
—
|
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: 1982-07-01 | Statement: [Mississippi University for Women v. Hogan, decidedDate, 1982-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidedDate Context triple: [Mississippi University for Women v. Hogan, decidedDate, 1982-07-01]
-
A.
decisionDate
chosen
Indicates the date on which a specific decision was formally made or finalized.
-
B.
appointedOn
Indicates the specific date or time at which an entity is formally assigned or designated to a role, position, or responsibility.
-
C.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
D.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
E.
depositionDate
Indicates the date on which something (such as a document, sample, or record) was formally submitted, filed, or placed into a repository or system.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e41753881909f0faed720cc31bc |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.