Triple
T28293528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atii Balbi |
E713492
|
entity |
| Predicate | hasGens |
P179920
|
FINISHED |
| Object | Atia gens |
—
|
NE NERFINISHED |
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: Atia gens | Statement: [Atii Balbi, hasGens, Atia gens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGens Context triple: [Atii Balbi, hasGens, Atia gens]
-
A.
hasGenera
Indicates a taxonomic relationship in which a higher-level group (such as a family or subfamily) includes one or more genera as its subordinate members.
-
B.
hasGenerations
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
C.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
D.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
E.
gens
Indicates a relationship where one entity generates, produces, or gives rise to another entity.
- F. None of above. chosen
Provenance (4 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 27, 2026, 11:30 p.m.