Triple
T11635984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubique |
E276519
|
entity |
| Predicate | mottoSignifies |
P25715
|
FINISHED |
| Object | presence in all major battles |
—
|
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: presence in all major battles | Statement: [Ubique, mottoSignifies, presence in all major battles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoSignifies Context triple: [Ubique, mottoSignifies, presence in all major battles]
-
A.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
B.
mottoInterpretation
Indicates the explanatory relationship between a motto and its intended meaning or message.
-
C.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
D.
mottoEmphasizes
chosen
Indicates that a motto highlights, stresses, or gives special importance to a particular idea, value, or theme.
-
E.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25d80208190b33e95db2e7cc276 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.