Triple
T30923143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High nobility of the Low Countries |
E787782
|
entity |
| Predicate | hadMemberFamily |
P170300
|
FINISHED |
| Object | House of Dampierre |
—
|
NE NERFINISHED |
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: House of Dampierre | Statement: [High nobility of the Low Countries, hadMemberFamily, House of Dampierre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMemberFamily Context triple: [High nobility of the Low Countries, hadMemberFamily, House of Dampierre]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
hasHouseholdMember
Indicates that one entity is a member of the same household as another entity.
-
C.
hasNotableFamilyMembers
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
-
D.
hasFamilyFriend
Indicates that one entity has another entity as a friend who is connected through family ties or close familial relationships.
-
E.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
- F. None of above. chosen
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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692b76a588190bde7401df721f418 |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:51 p.m.