Triple
T9510508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Anna of Orange-Nassau |
E229378
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Anna |
E161036
|
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: Anna | Statement: [Princess Anna of Orange-Nassau, givenName, Anna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anna Context triple: [Princess Anna of Orange-Nassau, givenName, Anna]
-
A.
Anna
Anna is the given name of Anna Murray Douglass, an African American abolitionist and the first wife of Frederick Douglass.
-
B.
Anna
Anna is a character from the video game "Surfacing," likely serving as a key figure in the game's narrative or player interactions.
-
C.
Anna
chosen
Anna is a feminine given name of Hebrew origin meaning "grace" or "favor," widely used across many cultures and languages.
-
D.
Anna
Anna is a character from the "Predator" franchise, appearing as one of the human figures caught up in the deadly encounters with the extraterrestrial hunter.
-
E.
Anna
Anna is a character appearing in the home-renovation reality TV series "Fixer Upper."
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9868616c8190856f89fecfa1a02e |
completed | April 1, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d139f7fa90819092e3fbcc62a9e5b9 |
completed | April 4, 2026, 4:19 p.m. |
Created at: March 30, 2026, 7:58 p.m.