Triple
T2204145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Sheridan |
E50556
|
entity |
| Predicate | hasPartInMottoOrQuote |
P14561
|
FINISHED |
| Object | “The only good Indian is a dead Indian” (attributed) |
—
|
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: “The only good Indian is a dead Indian” (attributed) | Statement: [Philip Sheridan, hasPartInMottoOrQuote, “The only good Indian is a dead Indian” (attributed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInMottoOrQuote Context triple: [Philip Sheridan, hasPartInMottoOrQuote, “The only good Indian is a dead Indian” (attributed)]
-
A.
hasPartInMotto
chosen
Indicates that something is included as a component or element within a motto.
-
B.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
C.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
D.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1baa0948190b07ffc347a4f714e |
completed | March 7, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69abbda8a6dc8190aa855ce2d17194b1 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.