Triple
T30529850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Cornelius Scipio Asina |
E776964
|
entity |
| Predicate | sharesConsulshipWith |
P169730
|
FINISHED |
| Object | Gaius Duilius |
—
|
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: Gaius Duilius | Statement: [Gnaeus Cornelius Scipio Asina, sharesConsulshipWith, Gaius Duilius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesConsulshipWith Context triple: [Gnaeus Cornelius Scipio Asina, sharesConsulshipWith, Gaius Duilius]
-
A.
consulshipWith
chosen
Indicates a relationship where two or more entities jointly hold, share, or are associated with the same consulship or consular office.
-
B.
consulship
Indicates the relationship in which an individual holds or exercises the office and powers of a consul.
-
C.
thirdConsul
Indicates that an entity holds the position or role of the third consul in a specified governing body or context.
-
D.
sharesSovereignWith
Indicates that two entities are under the authority of the same sovereign state or ruler.
-
E.
sharesSecretariatWith
Indicates that two entities are served or administered by the same secretariat or administrative office.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: April 29, 2026, 8:18 p.m.