Triple
T36402170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon boundary dispute |
E896659
|
entity |
| Predicate | U.S.Slogan |
P20424
|
FINISHED |
| Object | Fifty-Four Forty or Fight |
—
|
NE NERFINISHED |
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: Fifty-Four Forty or Fight | Statement: [Oregon boundary dispute, U.S.Slogan, Fifty-Four Forty or Fight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: U.S.Slogan Context triple: [Oregon boundary dispute, U.S.Slogan, Fifty-Four Forty or Fight]
-
A.
rallyingSloganOf
chosen
Indicates that a phrase or slogan is used as a unifying or motivational rallying cry associated with a particular group, movement, event, or cause.
-
B.
sloganUsedBy
Indicates that a particular slogan is employed or adopted by a specific entity (such as a person, organization, or brand) in its communication or branding.
-
C.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
-
D.
sloganInEnglish
Indicates that an entity’s slogan is expressed in the English language.
-
E.
associatedWithFamousSlogan
Indicates that an entity is connected to, known for, or commonly linked with a particular famous slogan.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.