Triple
T35056699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deaf Valley |
E1011486
|
entity |
| Predicate | appliedAsNicknameSince |
P48126
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Deaf Valley, appliedAsNicknameSince, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedAsNicknameSince Context triple: [Deaf Valley, appliedAsNicknameSince, 20th century]
-
A.
usedAsNicknameSince
chosen
Indicates that one entity has been used as a nickname for another entity starting from a specified point in time.
-
B.
replacedNicknameOf
Indicates that one nickname has been superseded or substituted by another nickname for the same entity.
-
C.
openedAsNicknameFor
Indicates that one entity was initially opened or launched using a particular nickname or informal name for it.
-
D.
usesNicknameIn
Indicates that one entity refers to another entity by a specific nickname within a particular context or setting.
-
E.
usesNicknameFor
Indicates that one entity habitually refers to another entity by a nickname rather than their formal or given 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:01 p.m.