Triple
T29928581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Locust Valley lockjaw |
E760151
|
entity |
| Predicate | stereotypedIn |
P97370
|
FINISHED |
| Object | American popular culture |
—
|
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: American popular culture | Statement: [Locust Valley lockjaw, stereotypedIn, American popular culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stereotypedIn Context triple: [Locust Valley lockjaw, stereotypedIn, American popular culture]
-
A.
notableStereotype
chosen
Indicates that a commonly recognized stereotype is associated with the subject in relation to the object.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
D.
standardizedIn
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
-
E.
traitStacking
Indicates the combination of multiple traits or characteristics within a single entity or context, typically to achieve a cumulative or enhanced effect.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677cecd448190be16545c3d34920e |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:17 p.m.