Triple
T22185903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comitia Curiata |
E548295
|
entity |
| Predicate | laterRepresentationBy |
P41058
|
FINISHED |
| Object | thirty lictors |
—
|
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: thirty lictors | Statement: [Comitia Curiata, laterRepresentationBy, thirty lictors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRepresentationBy Context triple: [Comitia Curiata, laterRepresentationBy, thirty lictors]
-
A.
laterRepresented
chosen
Indicates that one entity subsequently served as an official representative or agent for another entity at a later time.
-
B.
onceRepresentedBy
Indicates that an entity previously had another entity serving as its representative, but that representation is no longer current.
-
C.
formerRepresentation
Indicates that one entity previously served as the representative (e.g., legal, political, or organizational) of another entity, but no longer holds that role.
-
D.
representationIn
Indicates that one entity serves as a depiction, model, or stand-in for another entity within a given context or medium.
-
E.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa8f178819094d1556df5aee5b9 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.