Triple
T32019256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notre-Dame-des-Victoires Parish |
E817632
|
entity |
| Predicate | hasRecords |
P122753
|
FINISHED |
| Object | baptismal registers |
—
|
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: baptismal registers | Statement: [Notre-Dame-des-Victoires Parish, hasRecords, baptismal registers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecords Context triple: [Notre-Dame-des-Victoires Parish, hasRecords, baptismal registers]
-
A.
hasWrittenRecordsIn
Indicates that an entity has produced or maintains written records in a specified medium, format, or location.
-
B.
containsRecord
chosen
Indicates that one entity holds, includes, or stores a particular record within it.
-
C.
hasRecordCategory
Indicates that something is associated with, or classified under, a particular record category.
-
D.
hasSeriesRecord
Indicates that one entity maintains a documented record or history of another entity’s participation or performance within a series.
-
E.
hasWorkRecordedThere
Indicates that a person or creator has had their work documented, produced, or otherwise officially recorded at a particular place or institution.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
Created at: May 1, 2026, 12:16 a.m.