Triple
T14138081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columnae Herculis |
E350350
|
entity |
| Predicate | hasTraditionalMotto |
P38121
|
FINISHED |
| Object | Non plus ultra |
—
|
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: Non plus ultra | Statement: [Columnae Herculis, hasTraditionalMotto, Non plus ultra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalMotto Context triple: [Columnae Herculis, hasTraditionalMotto, Non plus ultra]
-
A.
hasMottoTradition
chosen
Indicates that an entity possesses a traditional motto associated with its identity or heritage.
-
B.
hasMottoOrigin
Indicates that a motto originates from, or is derived from, a particular source, place, or context.
-
C.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
D.
hasMottoAuthority
Indicates that an entity has the official power or right to establish, approve, or oversee the use of a motto for another entity.
-
E.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610fb86c81909eb26bf9c13696ca |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:39 a.m.