Triple
T4862835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grove City College v. Bell |
E108700
|
entity |
| Predicate | wasDecidedOn |
P29537
|
FINISHED |
| Object | February 28, 1984 |
—
|
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: February 28, 1984 | Statement: [Grove City College v. Bell, wasDecidedOn, February 28, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDecidedOn Context triple: [Grove City College v. Bell, wasDecidedOn, February 28, 1984]
-
A.
decidedIn
chosen
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
B.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
-
C.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
E.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d60e47c819094b5fbe883db4c15 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.