Triple
T30067889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormi Webster |
E764085
|
entity |
| Predicate | hasFirstNameFrom |
P195678
|
FINISHED |
| Object | English-language given names |
—
|
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: English-language given names | Statement: [Stormi Webster, hasFirstNameFrom, English-language given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstNameFrom Context triple: [Stormi Webster, hasFirstNameFrom, English-language given names]
-
A.
hasFirstNameOnly
Indicates that the entity is identified or recorded using only a first name, without any additional name components such as a middle or last name.
-
B.
hasFirstNameFromParent
Indicates that an entity’s first name is derived from or inherited from one of its parents’ names.
-
C.
hasGivenNames
Indicates that an entity possesses one or more personal (given) names assigned to it.
-
D.
hasFamilyNameInitial
Indicates that an entity’s family name begins with a specified initial letter or character.
-
E.
givenFirstAndMiddleNamesOf
Indicates that one entity has been provided with the first and middle names of another entity.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69fddf70ab10819088b76bd98e208354 |
completed | May 8, 2026, 1:04 p.m. |
Created at: April 29, 2026, 7 p.m.