Triple
T26954055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WASP elite |
E678848
|
entity |
| Predicate | perceivedCharacteristics |
P147578
|
FINISHED |
| Object | reserve and understatement |
—
|
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: reserve and understatement | Statement: [WASP elite, perceivedCharacteristics, reserve and understatement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedCharacteristics Context triple: [WASP elite, perceivedCharacteristics, reserve and understatement]
-
A.
perceivedAttribute
Indicates that one entity recognizes, interprets, or assigns a particular attribute or quality to another entity.
-
B.
perceivedCharacter
chosen
Indicates how one entity subjectively views or interprets the traits, qualities, or persona of another entity.
-
C.
valueCharacteristic
Indicates that one entity serves as a value or specific quantitative/qualitative measure that characterizes or describes another entity.
-
D.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
E.
termCharacteristics
Indicates the defining properties, attributes, or features that characterize a given term.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 6:26 a.m.