Triple
T20958970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lentulus Batiatus |
E516184
|
entity |
| Predicate | relationshipToGracchus |
P141855
|
FINISHED |
| Object | political contact |
—
|
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: political contact | Statement: [Lentulus Batiatus, relationshipToGracchus, political contact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToGracchus Context triple: [Lentulus Batiatus, relationshipToGracchus, political contact]
-
A.
relationshipToOctavian
Indicates the specific familial, political, or social relationship that one entity has to Octavian.
-
B.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
C.
relationshipToHeracles
Indicates the specific familial or social relationship that an entity has to Heracles.
-
D.
relationshipToPriam
Indicates a familial or social connection that someone has specifically with Priam.
-
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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6d6cd48190b83d1ceb1d0f6670 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 1:29 p.m.