Triple
T35805914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guerrero family |
E1035099
|
entity |
| Predicate | hasFamilyMottoOrCatchphrase |
P29651
|
FINISHED |
| Object | Lie, Cheat, Steal |
—
|
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: Lie, Cheat, Steal | Statement: [Guerrero family, hasFamilyMottoOrCatchphrase, Lie, Cheat, Steal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyMottoOrCatchphrase Context triple: [Guerrero family, hasFamilyMottoOrCatchphrase, Lie, Cheat, Steal]
-
A.
mottoOrNickname
Indicates that one entity serves as a motto, slogan, or nickname associated with another entity.
-
B.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
C.
usesMotto
chosen
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
D.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
E.
hasCatchphraseText
Indicates that an entity is associated with a specific catchphrase expressed as text.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 4:06 p.m.