Triple
T32210976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garland, Nebraska |
E822800
|
entity |
| Predicate | previousNameChangeReason |
P2136
|
FINISHED |
| Object | anti-German sentiment during World War I |
—
|
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: anti-German sentiment during World War I | Statement: [Garland, Nebraska, previousNameChangeReason, anti-German sentiment during World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNameChangeReason Context triple: [Garland, Nebraska, previousNameChangeReason, anti-German sentiment during World War I]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
C.
changedSurnameFrom
Indicates that an entity has adopted a new surname that was previously a different, specified surname.
-
D.
changedProfessionalNameFrom
Indicates that an entity has altered its professional or working name from a specified previous name.
-
E.
hasHistoricalNameChangeReason
Indicates that there is a specific reason or cause associated with a change in an entity’s historical name.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 12:37 a.m.