Triple
T33568306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnsburg, Germany |
E859821
|
entity |
| Predicate | isAncestralOriginOf |
P34787
|
FINISHED |
| Object | settlers of Johnsburg, Illinois |
—
|
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: settlers of Johnsburg, Illinois | Statement: [Johnsburg, Germany, isAncestralOriginOf, settlers of Johnsburg, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAncestralOriginOf Context triple: [Johnsburg, Germany, isAncestralOriginOf, settlers of Johnsburg, Illinois]
-
A.
proposedAsAncestralOriginOf
Indicates that something is suggested or hypothesized to be the ancestral source or origin of something else.
-
B.
mayIndicateAncestralOriginFrom
Indicates that one entity suggests or implies the ancestral origin or lineage of another entity.
-
C.
ancestralDomainOf
Indicates that one entity is the original or historically prior domain from which another domain is derived or descended.
-
D.
ancestralStatus
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
E.
hasAncestralRoots
chosen
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f741b6b88190b16bb2703678a37a |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.