Triple
T31790427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Estrées |
E811447
|
entity |
| Predicate | notableEcclesiasticalMember |
P92872
|
FINISHED |
| Object | César d’Estrées |
E2059093
|
NE 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: César d’Estrées | Statement: [House of Estrées, notableEcclesiasticalMember, César d’Estrées]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEcclesiasticalMember Context triple: [House of Estrées, notableEcclesiasticalMember, César d’Estrées]
-
A.
notableBishop
Indicates that a person holds or held the position of bishop and is recognized as particularly significant or distinguished in that role.
-
B.
hasNotableClergyman
chosen
Indicates that an entity is associated with a clergyman who is distinguished or notable in some recognized way.
-
C.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
D.
isEcclesiasticalHeadOf
Indicates that one entity serves as the highest religious or church authority for another entity.
-
E.
notableStaffMember
Indicates that a person is a distinguished or prominent member of an organization's staff.
- F. None of above.
Provenance (4 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3689af34e0819081d080a8d26e700e |
completed | June 20, 2026, 12:38 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:39 p.m.