Triple
T5339869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remonstrants |
E123917
|
entity |
| Predicate | laterGained |
P13710
|
FINISHED |
| Object | legal toleration in the Netherlands |
—
|
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: legal toleration in the Netherlands | Statement: [Remonstrants, laterGained, legal toleration in the Netherlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterGained Context triple: [Remonstrants, laterGained, legal toleration in the Netherlands]
-
A.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
B.
laterRaised
Indicates that one entity was raised, elevated, or brought up at a time subsequent to another referenced event or state.
-
C.
gainedFrom
Indicates that something is obtained, acquired, or derived as a result of a specified source or cause.
-
D.
laterLoyalty
Indicates that one entity becomes loyal to another at a later time, rather than from the outset of their relationship.
-
E.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.