Triple
T25651946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John T. Raulston |
E643124
|
entity |
| Predicate | notableTrialPresided |
P132428
|
FINISHED |
| Object | Scopes Monkey Trial |
—
|
NE NERFINISHED |
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: Scopes Monkey Trial | Statement: [John T. Raulston, notableTrialPresided, Scopes Monkey Trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTrialPresided Context triple: [John T. Raulston, notableTrialPresided, Scopes Monkey Trial]
-
A.
trialPresidedOver
chosen
Indicates that a particular judge or authority figure oversaw and directed the proceedings of a specific trial.
-
B.
defendantInNotableTrial
Indicates that an entity served as the defendant in a trial that is considered notable or historically significant.
-
C.
trialHeld
Indicates that a formal legal proceeding or court trial has taken place regarding a particular case or dispute.
-
D.
notableCourt
Indicates that a particular court is especially significant or noteworthy in relation to the subject.
-
E.
trialHeldIn
Indicates that a legal trial took place or was conducted within a specified location or jurisdiction.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 21, 2026, 6:25 p.m.