Triple
T30921294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notre-Dame des Anges |
E787729
|
entity |
| Predicate | isNameVariantOf |
P154137
|
FINISHED |
| Object | Our Lady of the Angels |
—
|
NE NERFINISHED |
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 of the Angels | Statement: [Notre-Dame des Anges, isNameVariantOf, Our Lady of the Angels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNameVariantOf Context triple: [Notre-Dame des Anges, isNameVariantOf, Our Lady of the Angels]
-
A.
nameHasVariant
Indicates that an entity’s name has an alternative or variant form.
-
B.
isSometimesUsedAsVariantOf
Indicates that one entity is occasionally employed as an alternative or substitute form of another entity, but not as its primary or standard version.
-
C.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
D.
likelyVariantOf
Indicates that one entity is probably a variant, version, or alternative form of another entity, based on available evidence or similarity.
-
E.
denotesVariantOf
chosen
Indicates that one entity is a variant or alternative form of another, typically sharing core identity or function with some differences.
- 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_69f692b56e288190805a577411a5e0c0 |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:51 p.m.