Triple
T22866298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aedui |
E567063
|
entity |
| Predicate | RomanTitle |
P136285
|
FINISHED |
| Object | brothers and kinsmen of the Roman people |
—
|
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: brothers and kinsmen of the Roman people | Statement: [Aedui, RomanTitle, brothers and kinsmen of the Roman people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanTitle Context triple: [Aedui, RomanTitle, brothers and kinsmen of the Roman people]
-
A.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
B.
ancientTitle
chosen
Indicates that an entity holds or is associated with a title or designation originating from ancient times.
-
C.
emperorTitle
Indicates that one entity holds the title or rank of emperor in relation to another entity.
-
D.
royalPrenomen
Indicates the formal throne name adopted by a monarch as part of their royal titulary.
-
E.
religiousTitle
Indicates that one entity holds or is referred to by a specific religious rank, honorific, or clerical title in relation 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f00f21081909b771610549c5757 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.