Triple
T4862836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grove City College v. Bell |
E108700
|
entity |
| Predicate | wasArguedOn |
P6917
|
FINISHED |
| Object | November 29, 1983 |
—
|
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: November 29, 1983 | Statement: [Grove City College v. Bell, wasArguedOn, November 29, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasArguedOn Context triple: [Grove City College v. Bell, wasArguedOn, November 29, 1983]
-
A.
rearguedWith
Indicates that one party presented arguments again or renewed a previous debate or legal argument with another party.
-
B.
arguedUnder
Indicates that one entity presented arguments or conducted a legal case under the supervision, authority, or guidance of another entity (such as a mentor, attorney, or judge).
-
C.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
D.
arguesThat
Indicates that one entity presents reasons or justification in support of a specific claim, position, or proposition held about another entity or topic.
-
E.
arguedDate
chosen
Indicates the date on which an argument, debate, or legal case was formally presented or argued.
- 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.