Triple
T1688704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Jennings Bryan |
E36500
|
entity |
| Predicate | roleInTrial |
P6384
|
FINISHED |
| Object | prosecution attorney in the Scopes Trial |
—
|
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: prosecution attorney in the Scopes Trial | Statement: [William Jennings Bryan, roleInTrial, prosecution attorney in the Scopes Trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTrial Context triple: [William Jennings Bryan, roleInTrial, prosecution attorney in the Scopes Trial]
-
A.
roleInResearch
Indicates that an entity participates in a research activity with a specified function, position, or responsibility within that research.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
E.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.