Triple
T5765044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman universalism |
E127190
|
entity |
| Predicate | hasMottoOrFormula |
P29651
|
FINISHED |
| Object | imperium sine fine |
—
|
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: imperium sine fine | Statement: [Roman universalism, hasMottoOrFormula, imperium sine fine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrFormula Context triple: [Roman universalism, hasMottoOrFormula, imperium sine fine]
-
A.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
C.
usesMotto
chosen
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
D.
hasPartInMotto
Indicates that something is included as a component or element within a motto.
-
E.
hasMottoContext
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.