Triple
T8466113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean de Brébeuf |
E200163
|
entity |
| Predicate | religiousOrderEntryDate |
P20285
|
FINISHED |
| Object | 1617 |
—
|
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: 1617 | Statement: [Jean de Brébeuf, religiousOrderEntryDate, 1617]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrderEntryDate Context triple: [Jean de Brébeuf, religiousOrderEntryDate, 1617]
-
A.
religiousOrderAssociation
chosen
Indicates that an entity is formally connected to, affiliated with, or a member of a particular religious order.
-
B.
religiousOrderSupported
Indicates that one entity provides support—such as resources, endorsement, or maintenance—to a particular religious order.
-
C.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
-
D.
religiousOrderRelations
Indicates a relationship in which one entity is connected to, affiliated with, or involved in the structure, activities, or authority of a religious order.
-
E.
religiousCouncilDate
Indicates the date on which a religious council or formal ecclesiastical assembly took place.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d17ec8819093becdaec750aff5 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.