Triple
T35861926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Calpurnius Piso (consul of AD 57) |
E1036973
|
entity |
| Predicate | belongsToGens |
P4276
|
FINISHED |
| Object | gens Calpurnia |
—
|
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: gens Calpurnia | Statement: [Lucius Calpurnius Piso (consul of AD 57), belongsToGens, gens Calpurnia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToGens Context triple: [Lucius Calpurnius Piso (consul of AD 57), belongsToGens, gens Calpurnia]
-
A.
associatedGens
Indicates a relationship where one entity is linked or connected to one or more genes in some relevant biological or functional context.
-
B.
belongsToGeneration
Indicates that an entity is associated with, classified within, or a member of a particular generation or generational group.
-
C.
hasGens
Indicates that an entity possesses or is associated with one or more generators (gens), typically as components, resources, or defining elements.
-
D.
usedByGens
Indicates that something is utilized or employed by one or more generations (or generational groups).
-
E.
belongsToFamily
chosen
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- F. None of above.
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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:06 p.m.