Triple
T243031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scopes "Monkey" Trial |
E4973
|
entity |
| Predicate | verdict |
P9727
|
FINISHED |
| Object | guilty |
—
|
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: guilty | Statement: [Scopes "Monkey" Trial, verdict, guilty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verdict Context triple: [Scopes "Monkey" Trial, verdict, guilty]
-
A.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
B.
judge
Indicates that one entity evaluates, forms an opinion about, or makes a decision regarding another entity or situation.
-
C.
unanimousDecision
Indicates that all relevant participants fully agree on a decision without any dissent.
-
D.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
-
E.
vote
Indicates that an entity formally expresses a choice or preference in a decision-making process, typically an election or poll.
- F. None of above. chosen
Provenance (4 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b62839c8190824064fe5da6a92a |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.