Triple
T13764754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathryn Ann Bailey |
E330709
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ann |
E33934
|
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: Ann | Statement: [Kathryn Ann Bailey, givenName, Ann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ann Context triple: [Kathryn Ann Bailey, givenName, Ann]
-
A.
Ann
chosen
Ann is a given name commonly used as a feminine first or middle name in English-speaking countries.
-
B.
Anna
Anna is the tragic, aristocratic heroine of Leo Tolstoy’s novel "Anna Karenina," whose passionate affair and struggle against societal norms lead to her downfall.
-
C.
Anna
Anna is the given name of pioneering Chinese American actress Anna May Wong, a trailblazing early Hollywood star and fashion icon.
-
D.
Anna
Anna is a spirited and optimistic princess from Disney's animated film "Frozen," known for her bravery, loyalty, and deep love for her sister Elsa.
-
E.
Anna
Anna of Moscow was a medieval Russian noblewoman and princess associated with the ruling dynasties of Muscovy.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de022690ac8190bd5410ecc659a2a7 |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b0724ab481908448d71a1bd02253 |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 10:10 p.m.