Triple
T30921291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notre-Dame des Anges |
E787729
|
entity |
| Predicate | hasTitleGroup |
P122743
|
FINISHED |
| Object | Our Lady titles |
—
|
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: Our Lady titles | Statement: [Notre-Dame des Anges, hasTitleGroup, Our Lady titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleGroup Context triple: [Notre-Dame des Anges, hasTitleGroup, Our Lady titles]
-
A.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasTitleName
chosen
Indicates that an entity possesses or is associated with a specific title or name.
-
D.
hasTitleScope
Indicates that a title or designation applies within a specific scope, context, or domain rather than universally.
-
E.
hasTitleBranch
Indicates that an entity holds or is associated with a specific title within a particular branch, division, or subdivision of an organization or structure.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 8:51 p.m.