Triple
T8569467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilma Rudolph |
E202890
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Wilma |
E512140
|
NE 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: Wilma | Statement: [Wilma Rudolph, givenName, Wilma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wilma Context triple: [Wilma Rudolph, givenName, Wilma]
-
A.
Wilma
chosen
Wilma was a catastrophic 2005 Atlantic hurricane that became one of the most intense on record, causing widespread destruction in the Caribbean and the United States.
-
B.
Vilma
Vilma is a feminine given name used in various cultures, often as a variant of Wilma or Vilhelmina.
-
C.
Yolanda
Yolanda is a feminine given name used in various cultures, often associated with figures in the arts, activism, and public life.
-
D.
Clarita
Clarita is a Spanish diminutive form of the given name Clara, often used as an affectionate or familiar variant.
-
E.
Irma
Irma is a feminine given name used in various European and Latin American cultures, often considered a variant or related form of names like Emma or Irmina.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea3f28608190a07be8b324669a12 |
completed | March 31, 2026, 3:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce897a958c81909b611fac377e26ca |
completed | April 2, 2026, 3:21 p.m. |
Created at: March 30, 2026, 6:21 p.m.