Triple
T10056586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duc d’Enghien |
E208876
|
entity |
| Predicate | associatedFamilyStatus |
P38221
|
FINISHED |
| Object | prince du sang |
—
|
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: prince du sang | Statement: [Duc d’Enghien, associatedFamilyStatus, prince du sang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedFamilyStatus Context triple: [Duc d’Enghien, associatedFamilyStatus, prince du sang]
-
A.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
-
B.
hasFamilyRole
chosen
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
-
E.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfae503881909b9f016da4e2207d |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.