Triple
T20019837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camillus |
E494826
|
entity |
| Predicate | notableEpithetOfBearer |
P23283
|
FINISHED |
| Object | second founder of Rome |
—
|
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: second founder of Rome | Statement: [Camillus, notableEpithetOfBearer, second founder of Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEpithetOfBearer Context triple: [Camillus, notableEpithetOfBearer, second founder of Rome]
-
A.
fieldOfNotableBearer
Indicates the professional or activity domain in which a notable bearer of a name, title, or identifier is recognized.
-
B.
notableNickname
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
C.
epithetOrTitle
chosen
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
D.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
-
E.
epithetOfOwner
Indicates that a descriptive epithet or nickname is associated with and refers specifically to the owner of an 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623f1598819097ad4fa392540901 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.