Triple
T17063921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Cambrai |
E414032
|
entity |
| Predicate | traditionallyStyled |
P60439
|
FINISHED |
| Object | Monseigneur |
—
|
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: Monseigneur | Statement: [Bishop of Cambrai, traditionallyStyled, Monseigneur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyStyled Context triple: [Bishop of Cambrai, traditionallyStyled, Monseigneur]
-
A.
traditionalStyle
chosen
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
B.
usesTraditionalDecoration
Indicates that an entity employs customary or historically established decorative styles or motifs in its design or presentation.
-
C.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
D.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
E.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db7f6a6081909bebce3ce925e663 |
completed | April 18, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.