Triple
T14805791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | government of Carthage |
E348030
|
entity |
| Predicate | suffetesComparedTo |
P11289
|
FINISHED |
| Object | Roman consuls |
—
|
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: Roman consuls | Statement: [government of Carthage, suffetesComparedTo, Roman consuls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suffetesComparedTo Context triple: [government of Carthage, suffetesComparedTo, Roman consuls]
-
A.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
B.
capitalCompared
Indicates a comparison between the capital cities associated with two entities, such as their relative status, attributes, or characteristics.
-
C.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
D.
surpasses
Indicates that one entity exceeds or goes beyond another in degree, quality, performance, or achievement.
-
E.
oftenContrastedWith
chosen
Indicates that one entity is frequently compared to another in a way that highlights their differences or opposing characteristics.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf32666081908e84f985c47eb963 |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:34 a.m.