Triple
T28237534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senatus Populusque Romanus dedication |
E711917
|
entity |
| Predicate | conjunctionUsed |
P51086
|
FINISHED |
| Object | -que enclitic |
—
|
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: -que enclitic | Statement: [Senatus Populusque Romanus dedication, conjunctionUsed, -que enclitic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conjunctionUsed Context triple: [Senatus Populusque Romanus dedication, conjunctionUsed, -que enclitic]
-
A.
junctionOf
Indicates that one or more entities meet or intersect at a common point, forming a junction between them.
-
B.
hasConjunction
chosen
Indicates that two or more entities are linked together by a coordinating conjunction, forming a combined or joint relationship.
-
C.
hasConjunctForms
Indicates that an entity is associated with one or more conjunct (combined or compound) forms of itself or related elements.
-
D.
isConjugatedTo
Indicates that two verb forms are related as different inflectional variants of the same verb through conjugation.
-
E.
isHeldInConjunctionWith
Indicates that one event, activity, or occurrence takes place together with another at the same time or as part of a combined arrangement.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c2f0248190a2bf87dceb15da01 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:56 p.m.