Triple
T36570713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSM |
E902113
|
entity |
| Predicate | designEraInfluence |
P132209
|
FINISHED |
| Object | 1970s tennis shoes |
—
|
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: 1970s tennis shoes | Statement: [GSM, designEraInfluence, 1970s tennis shoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designEraInfluence Context triple: [GSM, designEraInfluence, 1970s tennis shoes]
-
A.
curatesEra
Indicates a relationship where an entity organizes, selects, or manages items, information, or works specifically associated with a particular historical or thematic era.
-
B.
hasEraInfluence
chosen
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
C.
architecturalInfluence
Indicates that one architectural style, structure, or designer has had a formative impact on the design, style, or features of another.
-
D.
designInfluenceOn
Indicates that one design, designer, or design-related factor has an effect on shaping, guiding, or altering another design or design outcome.
-
E.
visualEra
Indicates the historical or stylistic period to which the visual appearance or design of something belongs.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:11 p.m.