Triple
T23547885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanoines réguliers |
E577954
|
entity |
| Predicate | présentsDans |
P102584
|
FINISHED |
| Object | diocèses catholiques |
—
|
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: diocèses catholiques | Statement: [Chanoines réguliers, présentsDans, diocèses catholiques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: présentsDans Context triple: [Chanoines réguliers, présentsDans, diocèses catholiques]
-
A.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
-
B.
presentsAt
Indicates that one entity delivers or gives a presentation, talk, or performance at a particular event, venue, or occasion.
-
C.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
D.
inscriptionPresence
Indicates that an inscription exists or is present on, within, or associated with a given entity.
-
E.
contemporaryPresenceIn
chosen
Indicates that an entity exists or is present in a particular place, context, or timeframe at the same time as another specified reference point or entity.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecc2af08190aec07cf9126d4e72 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.