Triple
T16008368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharpe family |
E388274
|
entity |
| Predicate | familyMottoOrReputation |
P20754
|
FINISHED |
| Object | financially ruined aristocrats |
—
|
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: financially ruined aristocrats | Statement: [Sharpe family, familyMottoOrReputation, financially ruined aristocrats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyMottoOrReputation Context triple: [Sharpe family, familyMottoOrReputation, financially ruined aristocrats]
-
A.
houseMotto
Indicates the official slogan or guiding phrase associated with a particular house or family.
-
B.
mottoReputation
chosen
Indicates that a particular motto is associated with and characterizes the reputation or public image of an entity.
-
C.
mottoOrNickname
Indicates that one entity serves as a motto, slogan, or nickname associated with another entity.
-
D.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
E.
mottoOrRole
Indicates that one entity serves as the motto, slogan, or role designation associated with another 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.