Triple
T31916783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Scribonius Libo (consul 34 BC) |
E814853
|
entity |
| Predicate | relationship to Pompey the Great |
P207545
|
FINISHED |
| Object | father‑in‑law |
—
|
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: father‑in‑law | Statement: [Lucius Scribonius Libo (consul 34 BC), relationship to Pompey the Great, father‑in‑law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationship to Pompey the Great Context triple: [Lucius Scribonius Libo (consul 34 BC), relationship to Pompey the Great, father‑in‑law]
-
A.
relationshipToOctavian
Indicates the specific familial, political, or social relationship that one entity has to Octavian.
-
B.
relationshipToCrassus
Indicates a relationship or association that one entity has with Crassus, specifying how it is connected or related to him.
-
C.
relationshipToGracchus
Indicates the specific familial, social, or political relationship that one entity has to Gracchus.
-
D.
precededInConsulshipBy
Indicates that one consul’s term of office occurred immediately before another consul’s term.
-
E.
laterRelationToRome
Indicates that one entity occurs or exists at a time later than the reference time associated with Rome.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:02 a.m.