Triple
T21149394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hold Tight, Hold Tight |
E521144
|
entity |
| Predicate | hasNotablePeriodOfPopularity |
P105129
|
FINISHED |
| Object | late 1930s |
—
|
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: late 1930s | Statement: [Hold Tight, Hold Tight, hasNotablePeriodOfPopularity, late 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePeriodOfPopularity Context triple: [Hold Tight, Hold Tight, hasNotablePeriodOfPopularity, late 1930s]
-
A.
notablePopularityPeriod
chosen
Indicates the time span during which something was especially popular or widely recognized.
-
B.
hasEnduringPopularityOn
Indicates that something continues to be widely liked, used, or appreciated on a particular platform, medium, or context over an extended period of time.
-
C.
hadPeakInfluencePeriod
Indicates the time span during which an entity exerted its greatest or most significant influence.
-
D.
associatedWithNotableEra
Indicates that something has a significant connection or relevance to a historically or culturally notable period of time.
-
E.
hasNotableRecordingPeriod
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723ffb578819080a000987459a8a5 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.