Triple
T1490558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | van Dam |
E29567
|
entity |
| Predicate | usedByPeopleOfAncestry |
P26561
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [van Dam, usedByPeopleOfAncestry, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByPeopleOfAncestry Context triple: [van Dam, usedByPeopleOfAncestry, Dutch]
-
A.
typicalAncestryDescription
chosen
Indicates the usual or most common ancestral background associated with an entity.
-
B.
usedByFamily
Indicates that something is regularly utilized or consumed by a family as a group.
-
C.
hasGenealogicalInterest
Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage of another entity.
-
D.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
E.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c233ec819087e1233af02aabfc |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.