Triple
T4499081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Maurice de Talleyrand-Périgord |
E100772
|
entity |
| Predicate | causeOfPhysicalCondition |
P11973
|
FINISHED |
| Object | congenital clubfoot |
—
|
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: congenital clubfoot | Statement: [Charles Maurice de Talleyrand-Périgord, causeOfPhysicalCondition, congenital clubfoot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfPhysicalCondition Context triple: [Charles Maurice de Talleyrand-Périgord, causeOfPhysicalCondition, congenital clubfoot]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causeOfDisability
chosen
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
C.
primaryCauseCategory
Indicates the main type or classification of cause responsible for an outcome or event.
-
D.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
E.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56c29868819097633c7cd398e865 |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.