Triple
T24749815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilke |
E619108
|
entity |
| Predicate | isRootFormOf |
P157091
|
FINISHED |
| Object | Wilkens |
—
|
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: Wilkens | Statement: [Wilke, isRootFormOf, Wilkens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRootFormOf Context triple: [Wilke, isRootFormOf, Wilkens]
-
A.
isRootOf
Indicates that one entity is the root or origin point from which another entity directly or indirectly descends or is derived.
-
B.
isRealFormOf
Indicates that one entity is the actual, physically existing or fully realized version of another entity, which may be abstract, conceptual, or a representation.
-
C.
isIntegralFormOf
Indicates that one entity is the integral (indefinite integral or antiderivative) form corresponding to another entity, typically a derivative or differential expression.
-
D.
isCanonicalFormOf
Indicates that one entity is the standard or officially accepted form or representation of another, often more variant, entity.
-
E.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:24 a.m.