Triple
T31376761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Cornelius Lentulus |
E800327
|
entity |
| Predicate | hasRelatives |
P7844
|
FINISHED |
| Object | Cornelii Lentuli officeholders |
—
|
LITERAL 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: Cornelii Lentuli officeholders | Statement: [Gnaeus Cornelius Lentulus, hasRelatives, Cornelii Lentuli officeholders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatives Context triple: [Gnaeus Cornelius Lentulus, hasRelatives, Cornelii Lentuli officeholders]
-
A.
closestLivingRelatives
Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
-
B.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
C.
hasNotableFamilyMembers
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
-
D.
siblingOrRelative
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
E.
hadRelative
Indicates that one entity had a familial relationship with another entity.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a0149447e448190b0480943de0691ee |
completed | May 11, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_6a0148e2c39c8190a3ad6ea6be902c04 |
completed | May 11, 2026, 3:11 a.m. |
Created at: April 29, 2026, 9:18 p.m.