Triple
T33930511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divus Romulus |
E869876
|
entity |
| Predicate | hasLatinHonorific |
P40137
|
FINISHED |
| Object | Divus Romulus |
—
|
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: Divus Romulus | Statement: [Divus Romulus, hasLatinHonorific, Divus Romulus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatinHonorific Context triple: [Divus Romulus, hasLatinHonorific, Divus Romulus]
-
A.
honorificDegree
Indicates that an entity has been awarded an honorary academic degree or title, typically in recognition of merit rather than completion of formal study.
-
B.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
-
C.
hasHonorificStatus
chosen
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to another entity.
-
D.
hasHonorificFrom
Indicates that one entity uses or receives a particular honorific title or form of address originating from another entity or source.
-
E.
hasHonorificBasis
Indicates that one entity serves as the basis or justification for assigning an honorific title or respectful form of address to 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: May 1, 2026, 1:49 a.m.