Triple
T4193148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juno |
E89080
|
entity |
| Predicate | epithet |
P743
|
FINISHED |
| Object | Juno Caprotina |
E89080
|
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: Juno Caprotina | Statement: [Juno, epithet, Juno Caprotina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Juno Caprotina Context triple: [Juno, epithet, Juno Caprotina]
-
A.
Julianna
Julianna is a feminine given name most notably borne by American actress Julianna Margulies.
-
B.
Juno
chosen
Juno is the ancient Roman queen of the gods, associated with marriage, childbirth, and the protection of the state.
-
C.
Juno
Juno is a 2007 coming-of-age comedy-drama film about a witty teenager dealing with an unplanned pregnancy, widely praised for its sharp dialogue and performances.
-
D.
Luciana
Luciana is a feminine given name of Latin origin, commonly used in Spanish- and Portuguese-speaking countries.
-
E.
Juno Pronuba
Juno Pronuba is an aspect of the Roman goddess Juno revered as the protector and patroness of marriage and married women.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0342c6048190835631649a14d304 |
completed | March 9, 2026, 5:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5961f0de081908e2b6bee1725b97e |
completed | March 14, 2026, 5:08 p.m. |
Created at: March 9, 2026, 3:46 p.m.