Triple
T32538992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintus Fabius Maximus Allobrogicus |
E831664
|
entity |
| Predicate | receivedCognomenFor |
P83928
|
FINISHED |
| Object | defeat of the Allobroges |
—
|
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: defeat of the Allobroges | Statement: [Quintus Fabius Maximus Allobrogicus, receivedCognomenFor, defeat of the Allobroges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedCognomenFor Context triple: [Quintus Fabius Maximus Allobrogicus, receivedCognomenFor, defeat of the Allobroges]
-
A.
cognomenOf
Indicates that one entity is the cognomen (surname or family name) of another entity.
-
B.
receivedHonorificNameFor
chosen
Indicates that an entity was given or acquired a particular honorific name or title in recognition of some status, role, or achievement.
-
C.
memberHasCognomen
Indicates that a member is associated with or bears a specific cognomen (surname or additional family name).
-
D.
grantedSurnameBy
Indicates that one entity formally conferred or assigned a surname to another entity.
-
E.
receivedClanNameFrom
Indicates that one entity obtained or was given its clan name from 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:02 a.m.