Triple
T22459056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douwes Dekker family |
E555183
|
entity |
| Predicate | namedAfterMember |
P63
|
FINISHED |
| Object | Douwes Dekker surname |
—
|
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: Douwes Dekker surname | Statement: [Douwes Dekker family, namedAfterMember, Douwes Dekker surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterMember Context triple: [Douwes Dekker family, namedAfterMember, Douwes Dekker surname]
-
A.
namedMember
Indicates that an entity is a member of a group, organization, or collection and is identified by a specific name within that membership context.
-
B.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
C.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
D.
namedAfterField
Indicates that one entity has been given a name derived from or in honor of another entity, typically a person, place, or thing.
-
E.
namedAfterSuccessor
Indicates that an entity is named after another entity that succeeds or follows it in time, position, or sequence.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b7e01fc8190825c3dc024484440 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.