Triple
T121509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semper Fidelis |
E2453
|
entity |
| Predicate | sloganType |
P504
|
FINISHED |
| Object | military slogan |
—
|
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 slogan | Statement: [Semper Fidelis, sloganType, military slogan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sloganType Context triple: [Semper Fidelis, sloganType, military slogan]
-
A.
mottoType
chosen
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
B.
sponsorType
Indicates the specific role or category of sponsorship that an entity provides in relation to another entity or event.
-
C.
campaignType
Indicates the specific category or kind of campaign an entity is associated with or participates in.
-
D.
sponsoringOrganizationType
Indicates the kind or category of organization that provides sponsorship or support in the described relationship or activity.
-
E.
historicalSloganDirectedAt
Indicates a relationship where a historical slogan was specifically addressed or targeted toward a particular audience, group, or 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a258fd278481908ad4498e03f38e2f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25647fe6081908cb0405266d35ff5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.