Triple
T26457497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beyond Horizons |
E665533
|
entity |
| Predicate | typeOfSlogan |
P54069
|
FINISHED |
| Object | military service motto |
—
|
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: military service motto | Statement: [Beyond Horizons, typeOfSlogan, military service motto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSlogan Context triple: [Beyond Horizons, typeOfSlogan, military service motto]
-
A.
sloganCategory
chosen
Indicates that a slogan is classified as belonging to a particular category or type.
-
B.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
-
C.
sloganInspired
Indicates that one slogan was created, influenced, or shaped by ideas, style, or content drawn from another source.
-
D.
hasSloganType
Indicates the specific category or type of slogan associated with an entity.
-
E.
sloganScope
Indicates the contextual scope or domain within which a particular slogan is intended to apply or be used.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 27, 2026, 12:10 a.m.