Triple
T28781021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRISPVS NOBIL CAES |
E726676
|
entity |
| Predicate | titleIndicated |
P38
|
FINISHED |
| Object | Nobilissimus Caesar |
—
|
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: Nobilissimus Caesar | Statement: [CRISPVS NOBIL CAES, titleIndicated, Nobilissimus Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleIndicated Context triple: [CRISPVS NOBIL CAES, titleIndicated, Nobilissimus Caesar]
-
A.
titleImplies
Indicates that holding or being assigned a particular title suggests or entails a certain role, status, or set of responsibilities.
-
B.
titleAffirms
Indicates that a title explicitly asserts, confirms, or supports the truth or validity of a particular claim, idea, or relationship.
-
C.
title
chosen
Indicates that one entity serves as the formal name or designation of another entity.
-
D.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
E.
titles
Indicates that one entity holds a formal title, designation, or name associated with 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 28, 2026, 6:19 a.m.