Triple
T2050336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonas Yoder |
E45549
|
entity |
| Predicate | argumentBasedOn |
P7446
|
FINISHED |
| Object | religious beliefs |
—
|
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: religious beliefs | Statement: [Jonas Yoder, argumentBasedOn, religious beliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: argumentBasedOn Context triple: [Jonas Yoder, argumentBasedOn, religious beliefs]
-
A.
arguesThat
Indicates that one entity presents reasons or justification in support of a specific claim, position, or proposition held about another entity or topic.
-
B.
areBasedOn
chosen
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
-
C.
decisionBasis
Indicates the underlying reason, criterion, or rationale on which a decision is made.
-
D.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
E.
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).
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98e10d48190bb96cd1f8ea3c08b |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.