Triple
T410572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canons of Dort |
E9480
|
entity |
| Predicate | formulatedDuring |
P9767
|
FINISHED |
| Object | 1618–1619 |
—
|
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: 1618–1619 | Statement: [Canons of Dort, formulatedDuring, 1618–1619]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formulatedDuring Context triple: [Canons of Dort, formulatedDuring, 1618–1619]
-
A.
formulatedIn
chosen
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
-
B.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
C.
enactedDuring
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
D.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
E.
developedAt
Indicates the place or location where something was created, built, or developed.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.