Triple
T12629789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vipsania |
E301609
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | gens Vipsania |
E301609
|
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: gens Vipsania | Statement: [Vipsania, usedBy, gens Vipsania]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: gens Vipsania Context triple: [Vipsania, usedBy, gens Vipsania]
-
A.
Vipsania
chosen
Vipsania is an ancient Roman feminine praenomen (personal name) used within the gens Vipsania.
-
B.
Vaccaria
Vaccaria is a small genus of flowering plants in the carnation family, known for species such as cowherb that are sometimes used in traditional medicine and ornamental gardening.
-
C.
Caesonia
Caesonia is a Roman cognomen (family name) used by women of the gens Atia in ancient Rome.
-
D.
Vesali
Vesali was an ancient city that served as a major early capital and cultural center of the Arakan (Rakhine) region in present-day Myanmar.
-
E.
Pison
Pison was a member of the ancient Roman Scribonia family, known by the cognomen "Piso," which was associated with several prominent statesmen and nobles of the late Republic and early Empire.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9610ce9e48190a496824002c0d2be |
completed | April 10, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65edafc7c819088bd641542a32e39 |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:15 p.m.