Triple
T5551927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honora Sneyd |
E145546
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Honora |
E243280
|
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: Honora | Statement: [Honora Sneyd, givenName, Honora]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Honora Context triple: [Honora Sneyd, givenName, Honora]
-
A.
Honora
chosen
Honora is a feminine given name of Latin origin meaning "honor" or "woman of honor."
-
B.
Cornelia
Cornelia is a feminine given name of Latin origin, historically associated with several notable women in European history.
-
C.
Constance
Constance is a feminine given name of Latin origin, historically associated with nobility and meaning steadfastness or constancy.
-
D.
Constance
Constance is a historic city on Lake Constance in present-day Germany, best known as the site of the early 15th-century Council of Constance that ended the Western Schism in the Catholic Church.
-
E.
Aemilia
Aemilia was a prominent Dutch warship that served as the flagship of the Dutch fleet during the Battle of the Downs in 1639.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ff872bc81908e14776f7ba4154e |
completed | March 22, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c028350bc08190a8b48893157b86a1 |
completed | March 22, 2026, 5:34 p.m. |
Created at: March 22, 2026, 3:35 p.m.